New submission from Karl Richter:
reproduction (on Ubuntu 14.04 amd64 with lxc 1.0.4) (with python 2.7.6 and
3.4.0)
# as root/with privileges
lxc-create -n ubuntu-trusty-amd64 -t ubuntu -- --arch amd64 --release trusty
lxc-stop -n ubuntu-trusty-amd64 # assert container isn't running
cd /var/lib/lxc
python
import shutil
shutil.copytree(ubuntu-trusty-amd64, ubuntu-trusty-amd64-orig)
# never returns (after a multiple of the time rsync needs (see below) no
more I/O operations)
verify behavior of rsync (3.1.0):
# as root/with privileges
rsync -a ubuntu-trusty-amd64/ ubuntu-trusty-amd64-orig/
# succeeds
If the container is shutdown it should no longer point to system resources, and
thus be able to get stuck on reading from a device file (and should rsync get
stuck as well in this case?).
It would be nice if python fails with an exception (or succeeds, of course)
instead of getting stuck.
--
messages: 221960
nosy: krichter
priority: normal
severity: normal
status: open
title: shutil.copytree hangs (on copying root directory of a lxc container)
(should succeed or raise exception nested)
versions: Python 2.7
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21885
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
