[comp.unix.microport] microport 2.3 release notes - problems dropped off the list

karl@sugar.UUCP (Karl Lehenbauer) (03/11/88)

Well, the problem report for Microport 2.3 that came separately in the mail
does not have the modem double panics and hangs listed as a problem at
all.  Closed that one out, did you?  Well, you didn't, you didn't, you didn't.

Also, in article <1438@qeztal.UUCP> Robert White makes mention of a
70,000 block upper limit on filesystems or they autotrash.  Is this
still true?  The bug list said about 130,000.  (I suppose it would
be 131071)  I am running a partition with 128,000 blocks.  Am I in 
trouble, or what?
-- 
"Lack of skill dictates economy of style." - Joey Ramone
..!uunet!nuchat!sugar!karl, Unix BBS (713) 438-5018

root@uwspan.UUCP (John Plocher) (03/17/88)

+---- karl@sugar.UUCP (Karl Lehenbauer) writes in <1542@sugar.UUCP> ----
|              The bug list said about 130,000.  (I suppose it would
| be 131071)  I am running a partition with 128,000 blocks.  Am I in 
| trouble, or what?
+----

The limit in 2.3 V/AT *is* 131071 512 byte blocks.

    (I know you know this, Karl, but others may not...)

This equals 65535  1024 byte blocks, and just *happens* to be the largest
value that can be stored in a 16 bit unsigned integer.  This integer is
used somewhere in the file system code and is the reason for the limit.

The fix is to simply change this to a   unsigned long   and get 32 bits out
of it.  But only Microport can do it... :-(


   -John

	

-- 
Comp.Unix.Microport is now unmoderated!  Use at your own risk :-)