Public bug reported:

Binary package hint: coreutils

Copied from the attached script that shows how to reproduce the problem:

#       If I use parted to create a partition table in a file representing
#       a disk image, it should take milliseconds to do.  This seems to be
#       the case when executing these steps directly:
#
#       use losetup (from live-build) to get a /dev/loopN
#       attach an empty file to the /dev/loopN
#       run a parted script on the empty file to create a partition table
#       release the /dev/loopN
#
#       However, when executed from within a chroot, this can take multiple
#       minutes, specifically when executing the parted step.
#
#       Requires:
#               -- A normal maverick desktop system
#               -- a lucid chroot built and available on that desktop system
#               -- "apt-get install live-build parted" in both the maverick
#                  desktop and the chroot
#
#       To show the problem, run this script.  First, without a chroot:
#               $ sudo ./problem.sh
#       then, use a chroot:
#               $ sudo ./problem.sh chroot-directory
#
#       The first run takes ~100-200 millisec on my system; the second run
#       with chroot takes ~6 *minutes*!  And, it does not matter whether or
#       not /dev is bind-mounted to /dev in the chroot -- either way takes
#       about the same amount of time.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: coreutils 8.5-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Oct 20 13:21:59 2010
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: coreutils

** Affects: coreutils (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug maverick

-- 
chroot loop devices stall for extremely long periods
https://bugs.launchpad.net/bugs/664115
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to