All of lore.kernel.org
 help / color / mirror / Atom feed
From: "K. Richard Pixley" <rich@noir.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: can't unmount
Date: Thu, 12 Aug 2010 08:58:41 -0700	[thread overview]
Message-ID: <4C641A31.4090603@noir.com> (raw)
In-Reply-To: <4C641969.9070405@noir.com>

  And should I be worried about what umount -l might be leaving behind?  
(eg, any unfreed kernel resources)  Or is that a reasonable way to deal 
with this situation on an ongoing basis?

--rich

On 8/12/10 08:55 , K. Richard Pixley wrote:
>  I'm running into a situation where I can't unmount a mounted 
> snapshot.  It shows "busy" even though neither lsof nor fuser show any 
> open files.  Umount -f doesn't work although umount -l does.
>
> Is there anything else I can do to debug this scenario or to clear the 
> busy status myself?  Or am I down to rebooting each time?
>
> This is on stock ubuntu-10.04, x86.
>
> --rich

  reply	other threads:[~2010-08-12 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 15:55 can't unmount K. Richard Pixley
2010-08-12 15:58 ` K. Richard Pixley [this message]
2010-08-12 17:46   ` C Anthony Risinger
2010-08-12 17:57     ` K. Richard Pixley
2010-08-12 19:15       ` C Anthony Risinger

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=4C641A31.4090603@noir.com \
    --to=rich@noir.com \
    --cc=linux-btrfs@vger.kernel.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.