From: Quinn Dunkan <quinn@groat.ugcs.caltech.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] dossrv panics
Date: Tue, 12 Mar 2002 20:27:40 -0800 [thread overview]
Message-ID: <20020313042745.B1C2E58829@groat.ugcs.caltech.edu> (raw)
dossrv tends to panic a lot on me. It often seems to happen when writing to
files which have been put there by linux, which leads me to believe that
linux's dos filesystem is doing something weird which is messing up dossrv.
The error msg is:
dossrv 45: panic putfat n=65528: file does not exist
Here's what dossrv -v has to say:
session...OK
attach(fid=275,uname="quinn",aname="/dev/sdC0/9fat",auth="")...alloc "/dev/sdC0/9fat", dev=3...[tread 0+0...done]magic: 0xeb 0x3c 0x90
version: "Plan9.00"
sectsize: 512
clustsize: 4
nresrv: 2
nfats: 2
rootsize: 512
volsize: 20482
mediadesc: 0xf8
fatsize: 20
trksize: 63
nheads: 128
nhidden: 4193280
bigvolsize: 20482
driveno: 128
reserved0: 0x00
bootsig: 0x29
volid: 0x003ffc2a
label: "CYLINDRICAL"
fatbits=16 (5104 clusters)...fat 0: 2...fat 1: 22...root: 42...data: 74...OK
...
"plan9path.py" 41 00 1b 0
"PLAN9P~1.PY " --a----- 19:47:42 102.03.12 30:40:00 102.03.12 102.03.12 1534 307
found
OK
remove(fid=254,name="plan9path.py")...[tread 27+0...done]dossrv 259: panic
putfat n=65528: file does not exist
From a cursory look at the src (and knowing almost nothing about FAT), it looks
like somehow dossrv got the idea that the file in question was on a cluster
which is too high (and is suspiciously close to 2^16---it's always 65528, even
for different files). Reading the files in question works fine, it just gets
confused on a write or delete. Oh, and it happens for short filenames too.
Before I possibly spend some time trying to figure out what cluster the file
actually is, and how dossrv figures out clusters, does this error look familiar
to anyone?
Random bit of learned-it-the-hard-way advice to other plan9 newbies:
don't name your kernel >8 chars, the loader doesn't seem to understand long
file names.
next reply other threads:[~2002-03-13 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 4:27 Quinn Dunkan [this message]
2002-03-13 5:21 Russ Cox
2002-03-13 7:00 ` Quinn Dunkan
2002-03-13 7:38 forsyth
2002-03-13 14:32 Russ Cox
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=20020313042745.B1C2E58829@groat.ugcs.caltech.edu \
--to=quinn@groat.ugcs.caltech.edu \
--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).