[Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
Launchpad Bug Tracker
1776626 at bugs.launchpad.net
Thu Oct 10 02:41:46 UTC 2019
This bug was fixed in the package systemd - 237-3ubuntu10.31
---------------
systemd (237-3ubuntu10.31) bionic; urgency=medium
[ Dimitri John Ledkov ]
* Add conflicts with upstart and systemd-shim. (LP: #1773859)
* d/p/debian/UBUNTU-units-disable-journald-watchdog.patch
- units: Disable journald Watchdog (LP: #1773148)
* d/p/cryptsetup-add-support-for-sector-size-option-8881.patch
- cryptsetup: add support for sector-size= option (LP: #1776626)
* d/p/systemctl-correctly-proceed-to-immediate-shutdown-if-sche.patch
- systemctl: correctly proceed to immediate shutdown if scheduling fails
(LP: #1670291)
* d/p/networkd-add-support-to-configure-IPv6-MTU-8664.patch
- networkd: add support to set IPv6MTUBytes (LP: #1671951)
-- Balint Reczey <rbalint at ubuntu.com> Mon, 30 Sep 2019 17:23:17 +0200
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to cryptsetup in Ubuntu.
https://bugs.launchpad.net/bugs/1776626
Title:
[18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
part
Status in Ubuntu on IBM z Systems:
Fix Released
Status in cryptsetup package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Fix Released
Status in cryptsetup source package in Bionic:
Won't Fix
Status in systemd source package in Bionic:
Fix Released
Bug description:
[Impact]
* cryptsetup in bionic supports creating luks volumes with a non-
standard sector-size option, and thus this option also needs to be
used when activating the LUKS volumes. Add sector-size= option support
to /etc/crypttab.
[Test Case]
* Create a plain LUKS volume with sector-size 4096
* Specify sector-size=4096 option in /etc/crypttab
* reload systemd, start systemd-cryptsetup at .service for that volume
* check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup)
[Regression Potential]
* This is an optional argument, not used by default. Currently custom
sector-size crypttab does not work correctly, and thus cannot regress.
[Other Info]
* Original bug report
Support fast clear key dm-crypt with 4k support
Extend /etc/crypttab to enable 4k sector support in plain mode
The proposed enhancements are posted on github, see
https://github.com/systemd/systemd/issues/8881
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions
More information about the foundations-bugs
mailing list