<div dir="ltr"><div class="gmail_quote"><div dir="ltr">Hello,<div><br></div><div><div>$ dpkg -l | grep lxc</div><div>ii liblxc1 1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers userspace tools (library)</div><div>ii lxc 1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers userspace tools</div><div>ii lxc-templates 1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers userspace tools (templates)</div><div>ii lxcfs 0.10-0ubuntu2.1 amd64 FUSE based filesystem for LXC</div><div>ii python3-lxc 1.1.5-0ubuntu0.15.10.3 amd64 Linux Containers userspace tools (Python 3.x bindings)</div></div><div><br></div><div><br></div><div>yesterday I needed to play with Moodle so I made a snapshot from another container I had.</div><div><br></div><div>$ sudo lxc-stop -n moodle</div><div>$ sudo lxc-clone -s moodle moodle30</div><div>$ sudo lxc-start -dn moodle30</div><div><br></div><div>I updated Moodle in the new container. Made some tests. And stoped the container.</div><div><br></div><div>Today, I restarted the container (moodle30) and ls -l showed some weird files, so I stoped the container.</div><div><br></div><div>ls -l /var/lib/lxc/moodle30/delta0/home/ubuntu/moodle shows:</div><div><br></div><div>-rw-rw-r-- 1 sysadmin sysadmin 42250 mar 8 01:36 config-dist.php<br></div><div><div>-rw-r--r-- 1 sysadmin sysadmin 691 mar 8 01:35 config.php</div><div>c--------- 1 root root 0, 0 mar 8 01:35 config.php~</div></div><div><br></div><div>Note config.php~</div><div><br></div><div>Now, after starting the container again, ls (inside the container) doesn't show those 'c' files.</div><div><br></div><div>Backend FS is ext4</div><div><br></div><div>Is this a know bug of -s with ext4 backend? Is there any way to avoid it (going to lvm/btrfs/zfs is not an option right now but I can accept it for future deployments).<br></div><div><br></div><div>Thanks!</div><div><br></div><div>Norberto</div></div>
</div><br></div>