<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.30.3">
</HEAD>
<BODY>
On Mon, 2010-09-27 at 13:16 +0100, Philip Rhoades wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
James,
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<<A HREF="mailto:phil@pricom.com.au">phil@pricom.com.au</A> <<A HREF="mailto:phil@pricom.com.au">mailto:phil@pricom.com.au</A>>> wrote:
>> > There seems to be only one file system mounted?
>>
>> Usually it's the bind mounts of /dev, /proc and /sys that don't get unmounted
>> first.
>
> and /var/cache/yum.
Did those but still couldn't umount:
/var/tmp/imgcreate-2A4KXU/install_root
</PRE>
</BLOCKQUOTE>
<BR>
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?)<BR>
<BR>
If that doesn't help, you can run<BR>
<BR>
lsof /var/tmp/imgcreate-2A4KXU/install_root<BR>
<BR>
to find out what process has that directory or something beneath it open.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
> And sometimes you have to delete the loop device manually:
>
> losetup -d /dev/loop0
I get:
loop: can't delete device /dev/loop0: Device or resource busy
</PRE>
</BLOCKQUOTE>
<BR>
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.<BR>
<BR>
James
</BODY>
</HTML>