From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] fossil riddle
Date: Thu, 29 Mar 2012 15:18:22 +0100 [thread overview]
Message-ID: <b3095a3a34b257acd051c527fa9fa78c@hamnavoe.com> (raw)
In-Reply-To: <8324903fd701463095501ba2faaa2bb6@hamnavoe.com>
The riddle revealed:
term% ls -l ape
d-rwxrwxr-x M 1003 miller miller 0 Mar 27 09:31 ape/9src
d-rwxrwxr-x M 1003 miller miller 0 Mar 27 09:31 ape/cmd
--rw-rw-r-- M 1003 miller miller 573 Feb 28 2002 ape/config
d-rwxrwxr-x M 1003 miller miller 0 Mar 27 09:31 ape/lib
--rw-rw-r-- M 1003 miller miller 368 Feb 28 2002 ape/mkfile
term% ls -l ape/cmd
ls: ape/cmd: 'ape/cmd' does not exist
term% cd ape
term% ls -l cmd
ls: cmd: 'cmd' disk is full
It's actually not specific to fossil, but an artefact of
9P2000. If a walk(5) down a multi-level path fails at the
first level, the server can return Rerror with an informative
message. But if it partially succeeds, it must return Rwalk
with a list of qids for the successfully traversed directories.
The kernel can't tell why the walk didn't complete, so it
takes a guess at "does not exist".
Possible solutions (if anyone cares):
- Next time 9P is revised, add a status string to Rwalk.
- In the kernel, if an N-level walk fails at level K (1 < K <= N),
retry as two sub-walks (length K-1 and 1) to get an Rwalk for
the failing level. If there's a race condition and the retry
succeeds, that's OK too.
- Change the error message to something more truthful like
"can't walk to ..."
prev parent reply other threads:[~2012-03-29 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 16:38 Richard Miller
2012-03-27 17:47 ` Nemo
2012-03-27 18:17 ` Richard Miller
2012-03-29 14:18 ` Richard Miller [this message]
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=b3095a3a34b257acd051c527fa9fa78c@hamnavoe.com \
--to=9fans@hamnavoe.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).