Quoting Cal Leeming [Simplicity Media Ltd] ([email protected]): > On Fri, Dec 13, 2013 at 9:46 AM, Jinn Ko <[email protected]> wrote: > > > When you run 'lsof | grep /tmp/lol/disk2.img' does that say '(deleted)' > > next to it? If so, it should also identify the process id holding the file > > handle open, which is preventing the release of the space. > > > > No, there is no entry in lsof for that file. > > It also doesn't seem to show any entry even when lxc-start is running. I'm > thinking perhaps it doesn't show up in here because it's a kernel module > maybe, but my knowledge on that isn't great. > > > > > > From the log output it looks like the failure to mount /proc inside your > > container causes a failure, so I haven't understood how it is that > > lxc-execute works. Therefore I'm wondering if the failure handling is > > missing the logic to release the mounted image. I'm curious to know if the > > space is released when /proc is properly mounted and the container comes up > > cleanly. > > > > Sadly I'm still able to reproduce this problem when the container comes up > cleanly. > > Scenario here; > http://pastebin.com/VB2iRQ6z
I tried to reproduce this on trusty (3.12 kernel) but the file went away fine for me. _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
