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.

Bug 1140199

Summary:	cryptsetup-reencrypt fails to write its log on some filesystems
Product:	Red Hat Enterprise Linux 7	Reporter:	Ondrej Kozina <okozina>
Component:	cryptsetup	Assignee:	Ondrej Kozina <okozina>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.0	CC:	agk, jstodola, mbroz, okozina, pholica, pkotvan, prajnoha
Target Milestone:	pre-dev-freeze	Keywords:	Triaged
Target Release:	7.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cryptsetup-1.6.6-2.el7	Doc Type:	Bug Fix
Doc Text:	cryptsetup-reencrypt with --use-directio parameter when invoked from directory residing in filesystem which was on top of block device with sector size <> 512B caused failure. The fix replaced O_DIRECT flag with O_SYNC flag for all open() calls related to reencrypt log. The O_SYNC flag is used whenever --use-fsync option is detected.	Story Points:	---
Clone Of:
Clones:	1140201 (view as bug list)		Environment:
Last Closed:	2015-03-05 11:07:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ondrej Kozina 2014-09-10 13:25:20 UTC

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-1.6.6-1.el7 (original version in RHEL7.0)
cryptsetup-1.6.3-2.el7 (rebased version in RHEL7.1)

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.

Comment 1 Milan Broz 2014-09-11 20:24:30 UTC

The --use-directio flag was intended for data access. The log file itself probably do not need to use O_DIRECT at all, fsync or similar mechanism should be enough (it is there to be able to continue correctly stopped encryption).

I will fix this upstream soon...

Comment 3 Ondrej Kozina 2014-09-24 07:47:51 UTC

fixed in upstream: https://code.google.com/p/cryptsetup/source/detail?r=3d6bcae84c5f55a82dc0056e3d7da33bee3f00b9

Comment 6 Peter Kotvan 2014-12-06 11:38:45 UTC

Verified on RHEL-7.1-20141204.2 with anaconda-19.31.111-1.el7.

Comment 8 errata-xmlrpc 2015-03-05 11:07:29 UTC

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-2015-0511.html