9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: 9fans@cse.psu.edu
Subject: [9fans] fs error msg: didn't like (1460 274) byte message
Date: Wed, 25 Sep 2002 01:25:35 +0200	[thread overview]
Message-ID: <200209242325.g8ONPZe24051@zamenhof.cs.utwente.nl> (raw)

Just had a problem copying/saving a file from acme at home
(over a right now not excitingly fast connection)
to the fake worm server at work.
When it happened, acme hang (until I fysically disrupted the connection
-- could not think of something else) and cp also hang.
(after disrupting the connection, acme returned to a usable state,
so I could save the file to local disk -- many thanks to the person
bringing up this kind of things (hanging fs connection) some days ago!)
When it happened, I had a 'C fs' window open, in which appeared:

didn't like 1460 byte message
didn't like 274 byte message

Scenario:
working at home on a laptop that has had the 60Mb update;
the kernel is a few days older, of september 18.
Because I have this funny router at the home  end of the cable
modem connection, and it does not let il through, I have

cpu%  cat /rc/bin/service/tcp564
#!/bin/rc
exec aux/trampoline il!super!9fs
cpu%

on the cpu server and run '9fs cpu' to connect to the file server.
(the cpu server is diskless and gets root from fs; also its
kernel is from september 18, I think).

The problem seems reproducible: when saving the remote file
from acme failed, I saved it locally and tried then copying it to fs,
with the same result. However, doing a 'cat > target'
in the cpu window, and pasting the text from the (short) file there,
followed by ^D was succesful (remember, cpu server gets root from fs).

The fs kernel is a bit old, from May 28. Can that explain this?

Is there anything easy I could try to get more insight?
I tried 'flag chat' on the fs, but that did not seem
to give info on the 'not-liked' packages -- but maybe I overlooked.

I'll keep the latop running and connected, in case there are some
things I could try.

Just tried to open a new window, run 9fs cpu, and tried again to
copy the same file from local disk to remote fs. Same result.

Axel (concerned, but still hoping for a simple explanation...)


             reply	other threads:[~2002-09-24 23:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 23:25 Axel Belinfante [this message]
2002-09-24 23:42 Russ Cox
2002-09-25 11:45 ` Axel Belinfante
2002-09-25 18:19 ` Axel Belinfante
2002-09-25 18:24 Russ Cox
2002-09-25 18:44 ` Axel Belinfante
2002-09-25 21:12 ` Axel Belinfante
2002-09-25 21:21 Russ Cox
2002-09-25 21:30 Russ Cox
2002-09-26  8:49 ` Axel Belinfante

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=200209242325.g8ONPZe24051@zamenhof.cs.utwente.nl \
    --to=axel.belinfante@cs.utwente.nl \
    --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).