process creating gigabyte files on encrypted filesystem fails with 100% cpu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ecryptfs-utils (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
On my system, several programs that create gigabyte sized files fail. the process allocates around a gigabyte then goes into a state where no more data is written to the disk, but the process consumes 100% of the cpu.
this issue first lead to the reporting of bug #925309, where the process was unkillable. The unkillable part seems to be fixed in the latest kernel package 3.0.0-16-generic #29-Ubuntu, but the failure of the programs that caused this is still present.
this problem is not only in qemu-kvm, creating disk images in VirtualBox also triggers this problem, although i currently have the VirtualBox packages installed instead of the Ubuntu VirtualBox packages.
Both of these applications work with no problem when writing to a non-encrypted file system.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: qemu-kvm 0.14.1+
ProcVersionSign
Uname: Linux 3.0.0-16-generic i686
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Sun Mar 11 13:27:08 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/qemu-img
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
MachineType: LENOVO 2958
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: qemu-kvm
UpgradeStatus: Upgraded to oneiric on 2012-01-14 (56 days ago)
dmi.bios.date: 05/05/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 18CN45WW(V2.54)
dmi.board.name: NITU1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2958
dmi.product.
dmi.sys.vendor: LENOVO
affects: | ubuntu → qemu-kvm (Ubuntu) |
Do you also get failures when you do
qemu-img create disk.img 10G
kvm -hda disk.img -cdrom precise-amd64.iso
in other words, when not pre-allocating the image?