This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author krichter
Recipients krichter
Date 2014-06-30.14:05:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1404137112.53.0.344262752308.issue21885@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-06-30 14:05:12krichtersetrecipients: + krichter
2014-06-30 14:05:12krichtersetmessageid: <1404137112.53.0.344262752308.issue21885@psf.upfronthosting.co.za>
2014-06-30 14:05:12krichterlinkissue21885 messages
2014-06-30 14:05:11krichtercreate