** Also affects: qemu (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importanc
Chris, please do, I just recreated the issue with the "uvt update -rf"
recipe from earlier; four of six VMs couldn't boot to a login: prompt,
presumably from this bug.
Linux hunt 3.13.0-65-generic #106-Ubuntu SMP Fri Oct 2 22:08:27 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
(I know, it misses this w
The fix is the following:
$ git describe --contains 6f30b7e37a8239f9d27db626a1d3427bc7951908
v4.0-rc1~1^2
I thought this was going to be queued up for stable, but doesn't look like
that happened.
If this still affects you in 3.13, 3.16, I can backport this patch. Let me know.
--
You received t
Is this still open against the 14.04.1 LTS kernel?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext3)
To man
This bug was fixed in the package linux - 3.19.0-12.12
---
linux (3.19.0-12.12) vivid; urgency=low
[ Andy Whitcroft ]
* [Packaging] do_common_tools should always be on
* [Packaging] Provides: virtualbox-guest-modules when appropriate
- LP: #1434579
[ Chris J Arges ]
*
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (e
Sent email to upstream stable to apply this bug to affected kernels.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext
** Description changed:
[Impact]
Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/
CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate
with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags.
[Test Case]
1) Setup ext4 ^extents, or ext3 filesyste
Woohoo! *Huge* thanks. This was a tricky one :)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext3)
To manage notific
Note there currently is a patch upstream:
https://lkml.org/lkml/2015/2/10/520
This fixes the original bug correctly without having to disable
ext4_punch_hole for indirect filesystems. Once this lands in Linus'
tree, I'll file an SRU to get this fixed across the board.
--
You received this bug no
This bug was fixed in the package linux - 3.18.0-13.14
---
linux (3.18.0-13.14) vivid; urgency=low
[ Andy Whitcroft ]
* hyper-v -- fix comment handing in /etc/network/interfaces
- LP: #1413020
[ Chris J Arges ]
* [Config] Add ibmvfc to d-i
- LP: #1416001
* SAUCE:
@josep-m-perez
Yes, this is an upstream bug. So it affects anyone using the right filesystem
and CONFIGs. Once we fix this upstream, then it will be submitted as a stable
kernel update and make its way into all stable kernels as applicable.
--
You received this bug notification because you are
** Description changed:
[Impact]
Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/
CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate
with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags. This seems to be a
regression in ext4_ind_remove_space intr
Apparently this bug is also present in Debian. In my case the corrupted
image was a windows one. When I run qemu-img check over it it will
complain about lots of clusters, and if I pass it the repair flag, then
it will end up crashing with the following message:
$ qemu-img check -r all windows.im
Sent e-mail upstream about this issue: http://marc.info/?l=linux-
fsdevel&m=142264422605440&w=2
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on
** Description changed:
+ [Impact]
+ Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/
CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate
with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags. This seems to be a
regression in ext4_ind_remove_space intr
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Change
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1292234
Title:
qcow2 image corruption on non-extent filesystems (ext3)
To manage notifications about this bug
** Summary changed:
- qcow2 image corruption in trusty (qemu 1.7 and 2.0 candidate)
+ qcow2 image corruption on non-extent filesystems (ext3)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bu
20 matches
Mail list logo
