From: "K. Richard Pixley" <rich@noir.com>
To: C Anthony Risinger <anthony@extof.me>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: can't unmount
Date: Thu, 12 Aug 2010 10:57:10 -0700 [thread overview]
Message-ID: <4C6435F6.6030708@noir.com> (raw)
In-Reply-To: <-3215279523596534788@unknownmsgid>
On 8/12/10 10:46 , C Anthony Risinger wrote:
> On Aug 12, 2010, at 10:58 AM, "K. Richard Pixley"<rich@noir.com> wrote:
>> 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?
>>
>> 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.
> You are lazy unmounting, as I understand, you are essentially just
> hiding the fact that the mount was busy to userspace... The mount will
> remain active in the kernel until you resolve whatever was stopping
> umount in the first place; kernel will then silently unmount.
Understood.
> Does this affect all of your mounted snapshots, or only a particular
> one?
I'm only mounting one at a time so I haven't noticed. Will check next
time it occurs.
--rich
next prev parent reply other threads:[~2010-08-12 17:57 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
2010-08-12 17:46 ` C Anthony Risinger
2010-08-12 17:57 ` K. Richard Pixley [this message]
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=4C6435F6.6030708@noir.com \
--to=rich@noir.com \
--cc=anthony@extof.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).