From: Daniel Phillips <phillips@bonn-fries.net>
To: "Amit S. Kale" <akale@veritas.com>, Sujal Shah <sujal@sujal.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
tigran@veritas.com
Subject: Re: FS Development (or interrupting ls)
Date: Fri, 3 Aug 2001 16:43:19 +0200 [thread overview]
Message-ID: <01080316431904.01827@starship> (raw)
In-Reply-To: <3B69EF9C.74DF18D6@sujal.net> <3B6A7A72.C2BF8C26@veritas.com>
In-Reply-To: <3B6A7A72.C2BF8C26@veritas.com>
On Friday 03 August 2001 12:18, Amit S. Kale wrote:
> Tigran Aivazian had a patch for doing a forced unmount.
> It will solve your problem. You can check whether he has a patch
> for the kernel you are using.
And please post that patch to the list when you find it, or the URL :-)
--
Daniel
> Sujal Shah wrote:
> > I'm working on a userspace filesystem daemon which replaces Venus (from
> > CODA) or podfuk (UserVFS) using the CODA driver. I'm still early in my
> > development process, but I've run into one frustrating problem. While
> > testing my code, I have started causing ls to hang.
> >
> > It keeps the directory open, which means I can't do things like, oh,
> > unmount the filesystem. :-) Anyone have any suggestions on recovering
> > gracefully when this happens short of rebooting (which is what I do
> > now)? Basically, 'ls' hangs, and can't be killed (even kill -9) and
> > 'lsof' lists the directory as open (which is furthered confirmed by
> > umount complaining about the filesystem being busy).
next prev parent reply other threads:[~2001-08-03 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B69EF9C.74DF18D6@sujal.net>
2001-08-03 10:18 ` Amit S. Kale
2001-08-03 10:38 ` [patch] (was " Tigran Aivazian
2001-08-03 14:43 ` Daniel Phillips [this message]
2001-08-03 15:13 ` Sujal Shah
2001-08-03 16:14 ` Tigran Aivazian
2001-08-03 14:31 ` Jan Harkes
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=01080316431904.01827@starship \
--to=phillips@bonn-fries.net \
--cc=akale@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sujal@sujal.net \
--cc=tigran@veritas.com \
/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®