From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200209242325.g8ONPZe24051@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24049.1032909934.1@zamenhof.cs.utwente.nl> Subject: [9fans] fs error msg: didn't like (1460 274) byte message Date: Wed, 25 Sep 2002 01:25:35 +0200 Topicbox-Message-UUID: f4757d86-eaca-11e9-9e20-41e7f4b1d025 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...)