Also here is the debug log; http://pastebin.com/Fh45gDLg
There's an entry that says rootfs is mounted but nothing to say it's been unmounted, and a look through the source code but I'm a bit out of my depth. I've attempted to reproduce the bug directly using losetup/mount, but it works without problem; http://pastebin.com/Vk4M360P Cal On Fri, Dec 13, 2013 at 4:54 AM, Cal Leeming [Simplicity Media Ltd] < [email protected]> wrote: > Sorry, I had sent the wrong link previously. > > The correct link is; > http://pastebin.com/chBWt5u1 > > Cal > > > On Fri, Dec 13, 2013 at 4:36 AM, Cal Leeming [Simplicity Media Ltd] < > [email protected]> wrote: > >> Not sure if this helps but here is a simple test scenario that will >> reproduce the problem; >> http://pastebin.com/V0GJsNcx >> >> Cal >> >> >> On Fri, Dec 13, 2013 at 3:59 AM, Cal Leeming [Simplicity Media Ltd] < >> [email protected]> wrote: >> >>> Hello, >>> >>> I'm able to create containers which use a single file for their rootfs; >>> >>> $ dd if=/dev/zero of=/rootfs.img bs=1 count=1024 >>> $ mkfs.ext4 /rootfs.img >>> -- other debootstrap commands here -- >>> >>> The image runs successfully in both lxc-start, lxc-start-ephemeral and >>> lxc-execute. >>> >>> However if I then attempt to delete the rootfs image after running >>> lxc-start or lxc-execute, the disk space is not given back and I have to >>> reboot in order to reclaim the disk space. >>> >>> Does anyone know why this might be happening? Perhaps LXC is keeping a >>> scale descriptor open somewhere? >>> >>> Any help would be really appreciated, can provide more info/debugging if >>> needed. >>> >>> Thanks >>> >>> Cal >>> >> >> >
_______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
