mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "colin" <colin@realtek.com.tw>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Solve the problem that umount will fail when an opened file isn't closed
Date: Mon, 19 Jun 2006 15:27:44 +0800	[thread overview]
Message-ID: <014501c69371$db472c20$106215ac@realtek.com.tw> (raw)
In-Reply-To: <Pine.LNX.4.61.0606161733030.13577@yvahk01.tjqt.qr>


Hi Jan,
I found that if the process doesn't close the file after usb disk is
unplugged, generic_shutdown_super won't be invoked.
generic_shutdown_super will be invoked right after all opened files are
closed.

Regards,
Colin


----- Original Message ----- 
From: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
To: "colin" <colin@realtek.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Sent: Friday, June 16, 2006 11:34 PM
Subject: Re: Solve the problem that umount will fail when an opened file
isn't closed


> >
> >Hi all,
> >I have implemented an auto-mount & auto-umount facility based on USB
> >hotplug.
> >An annoying problem will occur when some process doesn't close its open
file
> >and auto-umount is trying to umount that mount point after usb disk has
been
> >unplugged.
> >Is there any way to force it to be umounted in this situation?
> >
>
> fs/super.c:
>
>     /* Forget any remaining inodes */
>     if (invalidate_inodes(sb)) {
>         printk("VFS: Busy inodes after unmount of %s. "
>            "Self-destruct in 5 seconds.  Have a nice day...\n",
>            sb->s_id);
>     }
>
> That's what happens if you eject a CD. The box won't explode though.
>
>
> Jan Engelhardt
> --


  reply	other threads:[~2006-06-19  7:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16  2:56 colin
2006-06-16 15:34 ` Jan Engelhardt
2006-06-19  7:27   ` colin [this message]
2006-06-16 16:39 Mike Smullin
2006-06-19  2:36 ` colin

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='014501c69371$db472c20$106215ac@realtek.com.tw' \
    --to=colin@realtek.com.tw \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®