On Wed, Dec 08, 1999 at 02:09:35AM +0800, Ying-Chieh Liao wrote:
> > Hmm, how many files are stored on /vicepc? I haven't looked at the code
> 
> Here's my SrvLog that is about /vicepc :
> 
> 09:19:20 done:  78 files/dirs,  107920 blocks
> 09:19:20 done:  124 files/dirs, 334769 blocks
> 09:19:20 done:  201 files/dirs, 74143 blocks
> 09:19:20 done:  28 files/dirs,  1507 blocks
> 09:19:20 done:  17 files/dirs,  395 blocks
> 09:19:20 done:  79 files/dirs,  27408 blocks
> 09:19:20 done:  349 files/dirs, 4095 blocks
> 09:19:20 done:  74 files/dirs,  33102 blocks
> 09:19:20 done:  507 files/dirs, 25059 blocks
> 09:19:20 done:  9 files/dirs,   1501 blocks
> 09:19:20 done:  176 files/dirs, 72045 blocks
> 09:19:20 done:  495 files/dirs, 21841 blocks
> 09:19:20 done:  27 files/dirs,  8509 blocks
> 09:19:20 done:  353 files/dirs, 239236 blocks
> 09:19:20 done:  442 files/dirs, 55158 blocks
> 09:19:20 done:  37 files/dirs,  1896 blocks
> 09:19:20 done:  64 files/dirs,  14594 blocks
> 09:19:20 done:  950 files/dirs, 73650 blocks
> 09:19:20 done:  44 files/dirs,  4511 blocks

Total 4054 files, possibly double this amount if there are backup
volumes.

> > yet, but it sounds like there are no container files available anymore.
> > 
> > What settings did you use when initializing the partition with
> > makeftree? (i.e. what are the depth and width parameters for /vicepc in
> > /vice/db/vicetab)
> 
> width=8, depth=5

That should allow for a maximum of 8^5 inodes, or 32768. I don't
understand why it has run out of files, there should still be thousands
of free inodes left. Hmm, have to look into how the ftree allocation
works.

Jan