From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: [9fans] cfs
Date: Tue, 19 Jan 2021 22:50:47 +0000 [thread overview]
Message-ID: <3c920334cad4bdde4a7608c2ae6df186@quintile.net> (raw)
Hi all,
I am playing with cfs(4). It works nicely dialing to my fileserver but
fails if I try to use the existing /srv/boot channel.
failed with /srv/boot:
sceolan% 5.out -d -n -F /srv/boot -f $cfs -S /n/cache
<-client: Tversion tag 65535 msize 8216 version '9P2000'
->server: Tversion tag 65535 msize 8216 version '9P2000'
5.out: write failed, inappropriate use of fd
works using dial:
sceolan% 5.out -d -F /srv/boot -f $cfs -S /n/cache
<-client: Tversion tag 65535 msize 8216 version '9P2000'
->server: Tversion tag 65535 msize 8216 version '9P2000'
<-server: Rversion tag 65535 msize 8216 version '9P2000'
->client: Rversion tag 65535 msize 8216 version '9P2000'
<-client: Tauth tag 13 afid 402 uname steve aname
->server: Tauth tag 13 afid 402 uname steve aname
<-server: Rauth tag 13 qid (0000000000000192 0 A)
->client: Rauth tag 13 qid (0000000000000192 0 A)
<-client: Tread tag 13 fid 402 offset 0 count 2048
Note: using -n or not makes no differnce to the failed version,
though I would expect to need -n with /srv/boot.
The error occurs on the first write to /srv/boot.
I can mount /srv/boot with mount(1) without problems.
What have I missed?
-Steve
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T1ff0c2bf191f9858-M8e031b5e1276934aa63964f2
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next reply other threads:[~2021-01-20 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 22:50 Steve Simon [this message]
2021-01-20 16:52 ` [9fans] cfs Anthony Martin
2021-01-20 17:25 ` Richard Miller
-- strict thread matches above, loose matches on Subject: below --
2009-05-13 13:01 [9fans] cfs Steve Simon
2009-05-13 11:20 Steve Simon
2009-05-13 12:34 ` erik quanstrom
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=3c920334cad4bdde4a7608c2ae6df186@quintile.net \
--to=steve@quintile.net \
--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).