From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Message-ID: <20020810124440.C8538@cackle.proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [9fans] KFS magic size?
Date: Sat, 10 Aug 2002 12:44:40 +0200
Topicbox-Message-UUID: da0a756e-eaca-11e9-9e20-41e7f4b1d025

There seems to be an odd limit on file size with KFS.  This is what
it looks like:

	% dd -if /dev/zero -of zeroes -bs 1048576 -count 100
	dnodebuf: trip indirect
	write: file system full
	63+0 records in
	63+0 records out
	%

I picked this up while trying to build a 9660 image for a more
recent copy of the Plan 9 distribution and whereas the above occurred
under 3rd Edition Plan 9, my original attempts were foiled by a
4th Edition installation of KFS.  Curiously, disk/mk9660 crashed
and left an image 65816576 bytes in size, whereas the above dd and
an attempt at cp'ing the 9660 image to another file both produced
files of size 65814528, 2048 bytes fewer.  I must confess at this
point that I'm not entirely certain of the "cp" file size, but the
"dd" number did ring a bell.

The other oddity is that I did produce a 9660 image on a previous
occasion, although I don't recall the circumstances, so I must have
tickled a KFS problem in some fashion I hadn't done before.  What
comes to mind is the possibility that I may have used a bigger
block size, although I'm sure I'm using the same disks I had
configured previously.

My immediate requirement would be to create the image so I can dump
it to CD-RW (thanks for the wonderful interface!), but I'm very
curious about the cause of the problem and how to obviate it in
future.

++L