All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] problem with loop device
Date: Tue, 12 Jul 2005 17:19:01 +0100	[thread overview]
Message-ID: <200507121719.01279.paul@codesourcery.com> (raw)
In-Reply-To: <OF6D985696.BD15548B-ON8725703C.0053183F-0525703C.0053ADA6@us.ibm.com>

On Tuesday 12 July 2005 16:13, Matt Lawrence wrote:
> I'm running on CentOS4 with a 2.6.11 kernel.  After using losetup to
> configure loop0 and mounting /dev/loop0, I am unable to unmount it.  I keep
> getting "device is busy" message, but lsof doesn't show anything.
> Everything is being built automatically by a script, so I know I'm not
> leaving a terminal session using it as a working directory.  Any ideas?

Use fuser -m to figure out what's still using the mount.
Make sure you don't have any other filesystems mounted inside it.

Paul

  reply	other threads:[~2005-07-12 16:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 15:13 [Qemu-devel] problem with loop device Matt Lawrence
2005-07-12 16:19 ` Paul Brook [this message]
2005-07-12 18:19   ` Matt Lawrence
2005-07-12 19:18     ` Christian MICHON

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200507121719.01279.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.