On Mon, 2010-09-27 at 13:16 +0100, Philip Rhoades wrote:
On 2010-09-27 03:12, James Heather wrote:
> On Sun, 2010-09-26 at 18:01 +0100, Bruno Wolff III wrote:
>> On Sun, Sep 26, 2010 at 23:48:51 +1000,
>> Philip Rhoades<phil(a)pricom.com.au <mailto:firstname.lastname@example.org>>
>> > There seems to be only one file system mounted?
>> Usually it's the bind mounts of /dev, /proc and /sys that don't get
> and /var/cache/yum.
Did those but still couldn't umount:
Then something's still running that's using that directory or file. Have
you made sure that the shell you're using to umount doesn't have that
directory as its working directory? (And if you used 'su' to get to
root, is the user shell you came from currently in that directory?)
If that doesn't help, you can run
to find out what process has that directory or something beneath it
> And sometimes you have to delete the loop device manually:
> losetup -d /dev/loop0
loop: can't delete device /dev/loop0: Device or resource busy
Yes, you won't be able to delete the loop device until after you've
successfully umounted, because the install root is mounted via the
loopback device. When you've managed to umount everything, the losetup
-d should succeed.