From: "colin" <colin@realtek.com.tw>
To: "Mike Smullin" <mikesmullin@s161200816.onlinehome.us>,
"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 10:36:52 +0800 [thread overview]
Message-ID: <006f01c69349$394a8ac0$106215ac@realtek.com.tw> (raw)
In-Reply-To: <d5a2d4790606160939i50ca65dfn2a4d92bc9b4a0fb0@mail.gmail.com>
Hi Mike,
Do you want to see the hotplug agent code?
I can mail it to you and I would be very grateful if you can give me any
suggestion to improve it.
It will be used on a consumer product and would be better to be very stable.
Regards,
Colin
----- Original Message -----
From: "Mike Smullin" <mikesmullin@s161200816.onlinehome.us>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>; "colin"
<colin@realtek.com.tw>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, June 17, 2006 12:39 AM
Subject: Re: Solve the problem that umount will fail when an opened file
isn't closed
> Thanks for that, Jan. What a great idea!
>
> > >I have implemented an auto-mount & auto-umount
> > facility based on USB
> > >hotplug.
>
> Colin can you explain how you implemented this? I would like to try it,
too.
>
> Thanks,
> Mike
>
> --
> Mike Smullin
> "The day I come in front of the Gartner audience and say we have a
> better Unix than Linux, that'll be a good day" -- Steve Ballmer
> http://www.mikesmullin.com
>
> --- Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> > >
> > >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
> > --
> > -
> > To unsubscribe from this list: send the line
> > "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
next prev parent reply other threads:[~2006-06-19 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 16:39 Mike Smullin
2006-06-19 2:36 ` colin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-16 2:56 colin
2006-06-16 15:34 ` Jan Engelhardt
2006-06-19 7:27 ` 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='006f01c69349$394a8ac0$106215ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikesmullin@s161200816.onlinehome.us \
/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®