** Changed in: lvm2
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
Title:
pvmove causes file system corruption without
Updated package landed in release pocket - changing project entry to Fix
Released.
** Changed in: ubuntu-z-systems
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in
This bug was fixed in the package e2fsprogs - 1.45.1-1ubuntu1
---
e2fsprogs (1.45.1-1ubuntu1) eoan; urgency=medium
* Use 4k blocksize in all ext4 mke2fs.conf such that lvm migration
between non-4k PVs and 4k PVs works irrespective of the volume
size. LP: #1817097
--
Modified version e2fsprogs 1.45.1-1ubuntu1 still in eoan-proposed.
Once it left proposed this ticket will be changed to Fix Released (e2fsprogs
and project).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in
With Eoan we now always default to 4k, hence Fix Released in e2fsprogs
and the project.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
Title:
pvmove causes file
** Also affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: e2fsprogs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch
Decreasing importance from critical to medium, because the bug is known to the
community, it is already discussed in RH Bug 1669751, and here
https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html /
https://www.redhat.com/archives/linux-lvm/2019-March/msg0.html, and not
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1669751.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
/etc/mke2fs.conf:
[defaults]
blocksize = 4096
[fs_types]
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
We default to 4k, unless one is formatting small filesystems which from manpage:
If the filesystem size
This is a well-known upstream issue/bug.
This is not s390x, Ubuntu 18.10, any other Ubuntu release specific.
There is no dataloss -> one can execute pvmove operation in reverse (or i guess
onto any 512 sector size PV) to mount the filesystems again.
Thus this is not critical at all.
Also, I am
Ok, reproduced this on x86_64 with raw files which are in multiples of
4k.
This is not an architecture specific issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development
release).
I am failing to produce a mixed blocksize cryptsetup device:
$ sudo cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
is
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1817097
Title:
pvmove causes file system
** Package changed: linux (Ubuntu) => lvm2 (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
** Changed in: ubuntu-z-systems
Importance:
14 matches
Mail list logo
