<p dir="ltr">I've read that mailing list post yesterday, too and was actually hoping this could solve the mount issue. When I looked at it, it seems that this patch hasnt been merged into the github repo yet, correct?</p>
<p dir="ltr">Will try it and let you know.</p>
<div class="gmail_quote">On Nov 26, 2014 6:35 AM, "Serge Hallyn" <<a href="mailto:serge.hallyn@ubuntu.com">serge.hallyn@ubuntu.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Quoting Claudio Kuenzler (<a href="mailto:ck@claudiokuenzler.com">ck@claudiokuenzler.com</a>):<br>
> Hello all,<br>
><br>
> OS: Ubuntu 14.04.1 LTS<br>
> LXC Version: 1.0.6-0ubuntu0.1<br>
><br>
> Experienced a weird issue when I tried to launch a container which mounts<br>
> an additional logical volume (ext4 formatted) through the container's fstab<br>
> file:<br>
><br>
> # cat /var/lib/lxc/mycontainer/fstab<br>
> /dev/vglxc/apps mnt/apps ext4 ro 0 0<br>
><br>
> This LV is already mounted on the physical host:<br>
><br>
> # mount /dev/vglxc/apps /mnt<br>
><br>
> Now when I try to launch the container, I get the following error:<br>
><br>
> # lxc-start -n mycontainer -l trace -o mycontainer.out<br>
> lxc-start: Device or resource busy - failed to mount '/dev/vglxc/apps' on<br>
> '/usr/lib/x86_64-linux-gnu/lxc/mnt/apps'<br>
> lxc-start: failed to setup the mounts for 'mycontainer'<br>
> lxc-start: failed to setup the container<br>
> lxc-start: invalid sequence number 1. expected 2<br>
> lxc-start: failed to spawn 'mycontainer'<br>
> lxc-start: The container failed to start.<br>
> lxc-start: Additional information can be obtained by setting the --logfile<br>
> and --logpriority options.<br>
><br>
> In the output file the following information is shown:<br>
><br>
> lxc-start 1416921918.699 INFO lxc_conf - Autodev not required.<br>
> lxc-start 1416921918.699 ERROR lxc_conf - Device or resource busy<br>
> - failed to mount '/dev/vglxc/apps' on<br>
> '/usr/lib/x86_64-linux-gnu/lxc/mnt/apps'<br>
> lxc-start 1416921918.699 ERROR lxc_conf - failed to setup the<br>
> mounts for 'mycontainer'<br>
><br>
> When I change the mount option in the container's fstab file from "ro" to<br>
> "defaults" (or basically "rw"), the container starts up:<br>
><br>
> # cat /var/lib/lxc/mycontainer/fstab<br>
> /dev/vglxc/apps mnt/apps ext4 defaults 0 0<br>
><br>
> # lxc-start -n mycontainer -l trace -o mycontainer.out<br>
><br>
> lxc-start 1416921799.912 INFO lxc_conf - Autodev not required.<br>
> lxc-start 1416921799.912 DEBUG lxc_conf - mounted<br>
> '/dev/vglxc/apps' on '/usr/lib/x86_64-linux-gnu/lxc/mnt/apps', type 'ext4'<br>
><br>
> If the LV /dev/vglxc/apps is nowhere mounted yet, the container starts up -<br>
> with the read only mount option, too.<br>
><br>
> Is this a (known) bug I ran into?<br>
<br>
I think it is. Can you please try with this patch:<br>
<br>
<a href="https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-November/010876.html" target="_blank">https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-November/010876.html</a><br>
<br>
applied?<br>
_______________________________________________<br>
lxc-users mailing list<br>
<a href="mailto:lxc-users@lists.linuxcontainers.org">lxc-users@lists.linuxcontainers.org</a><br>
<a href="http://lists.linuxcontainers.org/listinfo/lxc-users" target="_blank">http://lists.linuxcontainers.org/listinfo/lxc-users</a></blockquote></div>