Newsgroups: comp.os.minix
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!Germany.EU.net!zib-berlin.de!unlisys!bercos.de!hk
From: hk@bercos.de (Helge Kruse)
Subject: Re: FS size supported in 1.7
X-Newsreader: TIN [version 1.2 PL2]
Reply-To: hk@bercos.de
Organization: BERCOS GmbH Berlin, Germany
Message-ID: <DK1JEA.A41@bercos.de>
References: <DJzBDs.4J7@bercos.de> <DJzzp7.EIt.0.-s@cs.vu.nl>
Date: Sat, 23 Dec 1995 13:13:21 GMT
Lines: 22

Kees J Bot (kjb@cs.vu.nl) wrote:
: hk@bercos.de (Helge Kruse) writes:

: Minix 1.7 uses a new file system type that has 32 bit block numbers.
: In theory this means a 4 G upper limit, but in practice one is
: constrained by lack of memory, or lack of inodes (still a 16 bit inode
: number.)  So mkfs has a limit of 128 Mb in 16 bit mode, and 256 Mb in 32
: bit mode.  That should be enough for Minix.

Thank you for information. But I think about a file server. Disks with
Gigabytes are available and so it's interesting to increase the 256 Mb
Limit. The inode number should'nt be a problem, since it's a limit
for the number of files. Large files doesn't consume much inode.
Isn't it?

BTW: How does Minix (old) FS acces more than 64M? I saw the BLOCKS_SIZE
defined as 1024 Bytes. 

Regards,
  Helge
: 	                        Kees J. Bot  (kjb@cs.vu.nl)
: 	              Systems Programmer, Vrije Universiteit Amsterdam
