[systemd-bugs] [Bug 68369] systemd-nspawn fails to start dirty rootfs

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 29 02:57:41 PDT 2013


https://bugs.freedesktop.org/show_bug.cgi?id=68369

--- Comment #2 from Laszlo Papp <lpapp at kde.org> ---
I experience similar issues with ext 4. Is there any workaround? I basically
moved /mnt/wheezy to my home due to space concerns. Then, it got broken all of
a sudden.

sudo systemd-nspawn
[sudo] password for lpapp: 
Spawning namespace container on /home/lpapp/Projects/chroot/wheezy (console is
/dev/pts/1).
Init process in the container running as PID 787.
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
mknod(/home/lpapp/Projects/chroot/wheezy) failed: File exists
Container failed with error code 1.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130829/0eb6d151/attachment.html>


More information about the systemd-bugs mailing list