Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!ig!uwmcsd1!nic.MR.NET!shamash!nis!ems!pwcs!elric!hawkmoon!root
From: root@hawkmoon.MN.ORG (Admin)
Newsgroups: comp.unix.microport
Subject: long mount paths
Keywords: df, mount, V/386 3.0-2.2
Message-ID: <363@hawkmoon.MN.ORG>
Date: 23 Sep 88 13:51:05 GMT
Organization: One of the Eternal Champions - Richfield, MN, 554232523, USA
Lines: 50


I have been fiddling with the jetroff distribution and decided, due to a lack
of disk space to put the fonts by themselves on a floppy and mount it thus:

$ mount /dev/dsk/f0q15dt ~det/src/jetroff/font/devjet/pk

But, then note the following output from df:
$ df
/         (/dev/dsk/0s1    ):     5484 blocks     2002 i-nodes
/usr      (/dev/dsk/0s3    ):    12458 blocks     5662 i-nodes
/usr/users (/dev/dsk/0s4    ):     5076 blocks     1000 i-nodes
/usr/ubin (/dev/dsk/0s8    ):     3970 blocks       73 i-nodes
/usr/spool/uucp (/dev/dsk/0s5    ):     5064 blocks     1365 i-nodes
/usr/spool/news (/dev/dsk/1s3    ):    18160 blocks    12523 i-nodes
/usr/users/det/src/jetroff/font/ (/dev/dsk/f0q15dt):     5076 blocks*    1000 i-nodes

The number of inodes and blocks is incorrect (in addition to the mount point
being truncated, but thats not a big beef).
I suspect that df is getting lost after a certain number of chars in the path
and just printing garbage.  (ooohhh, that smell! (:-))

$ labelit /dev/dsk/f0q15dt
Current fsname: pk, Current volname: 01M_T7, Blocks: 2400, Inodes: 240
FS Units: 1Kb, Date last modified: Fri Sep 23 08:36:57 1988

Then after i had done a:

$ du pk
1561	/usr/tmp/fonts/font/devjet/pk
$ find pk -print|cpio -padmv ~det/src/jetroff/font/devjet/pk

it ran out disk space on the floppy (the floppy was empty, thus had ~2400
blocks on it) and then the device became inaccessable and the directory itself
dissappeared!

Anyone seen this problem or have a fix for it?

Ps. Normally i would have just sent this to uport, but my mail seems to be
    mysteriously dissappearing.. (:-(

PPs.  Please, unless there is a *real* reason why i shouldn't mount a device on
      such a long path name (like its stated somewhere in the documentation
      that one shouldn't exceed X chars in the path name, etc), don't flame me
      for using a path name like the above.  I don't think its terribly
      unreasonable.
-- 
Derek Terveer		root@hawkmoon.MN.ORG
			w(612)681-6986	h(612)688-0667

"A proper king is crowned" -- Thomas B. Costain