Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1140199 +++
Description of problem:
cryptsetup-reencrypt utility is unable to performs I/O oper. with O_DIRECT flag on any filesystem imposing restrictions to O_DIRECT operations with minimal transfer size <> 512B. This results in cryptsetup-reencrypt being unable to read/write its log files using O_DIRECT on such filesystems.
Version-Release number of selected component (if applicable):
cryptsetup-reencrypt-1.6.4-1.el6
How reproducible: always
Steps to Reproduce:
1. create 4K physical sector size block device (modprobe scsi_debug sector_size=4096 dev_size_mb=100)
2. mkfs.xfs /dev/sdx (/dev/sdx being 4K sector blockdev)
3. mount /dev/sdx /mnt/test
4. cd /mnt/test
5. fallocate -l $[10*1024*1024] /tmp/test_luks.img
6. echo aaa | cryptsetup --force-password luksFormat /tmp/test_luks.img
7. echo aaa | cryptsetup-reencrypt --debug /tmp/test_luks.img --use-directio
Actual results:
Cannot write reencryption log file.
Cannot open reencryption log file.
and retval=1
Expected results:
device reencrypted w/o failures
Propsed workaround: remove --use-directio parameter from command or move working directory to fs which has not such restrictions.
Removing --use-directio param will unfortunately also avoid O_DIRECT flag from i/o operations landing on reencrypted luks device itself.
Retested with cryptsetup-reencrypt-1.6.4-2.el6, reencryption finished successfully, log files were successfully created during the process and removed at the end:
LUKS-e75541c9-d62e-4a7c-9142-6458e67b9f9f.log
LUKS-e75541c9-d62e-4a7c-9142-6458e67b9f9f.org
LUKS-e75541c9-d62e-4a7c-9142-6458e67b9f9f.new
Moving to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-0946.html