qemu does not call unlink() on temp files in snapshot mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
== overview ==
When booting guests in snapshot mode qemu never calls unlink()
on the files storing changes to the images. This results in large amounts of
disk space being used over time.
This bug seems to have been introduced by qemu git commit b6ce07aa83bdee3
== steps to reproduce ==
1) Boot a guest like so:
qemu -m 512 -drive
file=/scratch/
== actual results ==
/tmp/vl.* files are created and never unlinked/deleted. for example:
mdroth@
[1] 24080
mdroth@
-rw------- 1 mdroth mdroth 262144 2010-06-22 14:21 /tmp/vl.tFSAmR
mdroth@
/tmp/vl.tFSAmR: 24080
== expected results ==
temporary files should immediately be unlink()'ed and not be present in the file
listing.
== system details ==
mdroth@
Linux illuin 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
latest commit (cada87c432e3b9
mdroth@
QEMU emulator version 0.12.50, Copyright (c) 2003-2008 Fabrice Bellard
Changed in qemu: | |
status: | Fix Committed → Fix Released |
Does not seem to happen anymore:
strace -etrace=unlink -esignal= -f ./qemu -drive file=/dev/ null,snapshot= on "/tmp/vl. jUbLWz" ) = 0
unlink(