From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Vacfs/9pfuse problems?
Date: Wed, 10 Sep 2008 12:25:41 +0800 [thread overview]
Message-ID: <140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com> (raw)
In-Reply-To: <20080909134936.GB10171@meep>
On Tue, Sep 9, 2008 at 9:49 PM, Venkatesh Srinivas <me@acm.jhu.edu> wrote:
> I've been having some trouble with vacfs and 9pfuse.
> If I Control-C any I/O operations, though, vacfs just 'goes away', Linux
> complains about the transport endpoint being disconnected.
>
> Also, running 'find' causes problems - after processing a small number
> of directories, find stops finding new files and returns 'permission
> denied' for directories,
I see the same 9pfuse behaviour mounting ircfs or u9fs at work. If I
interrupt some I/O, I lose the mount.
Haven't seen the find problem, 9pfuse -D might be instructive there.
-sqweek
next prev parent reply other threads:[~2008-09-10 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 13:49 Venkatesh Srinivas
2008-09-10 4:25 ` sqweek [this message]
2008-09-10 14:41 ` Russ Cox
2008-09-11 5:46 ` sqweek
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=140e7ec30809092125i30635834kedce2d37dda93061@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@9fans.net \
/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).