9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: [9fans] lnfs
Date: Tue,  1 Oct 2002 09:18:49 +0100	[thread overview]
Message-ID: <97967b679371324c95efff80d254b753@9fs.org> (raw)

Is it expected that lnfs can support several instances of it running
on the same file tree?

It looks that way in that it reloads the the name file before walks
and creates.

But there is no retry around the write of a new entry in newname().
So one instance might create a long named file, and fail to flush it
to .longnames.  Another instance would then not have a translation for
the base32 name it finds in the directory during a walk.

I accept that the windows are small, but I'm searching for an
explanation for some strange behaviour I saw yesterday.



             reply	other threads:[~2002-10-01  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  8:18 nigel [this message]
2002-10-01 13:51 presotto
2002-10-02  4:29 nigel
2002-10-02 13:22 ` david presotto
2002-10-02  5:08 Russ Cox
2002-10-02 13:15 ` david presotto
2002-10-02  7:05 Geoff Collyer

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=97967b679371324c95efff80d254b753@9fs.org \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).