From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
From: Quinn Dunkan <quinn@groat.ugcs.caltech.edu>
Message-Id: <20020313042745.B1C2E58829@groat.ugcs.caltech.edu>
Subject: [9fans] dossrv panics
Date: Tue, 12 Mar 2002 20:27:40 -0800
Topicbox-Message-UUID: 658daa30-eaca-11e9-9e20-41e7f4b1d025

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.