home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!sun-barr!sh.wide!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
- From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
- Newsgroups: comp.unix.admin
- Subject: Re: FDDI, 20+GB unix file partitions, Remote NFS mount IBM to Sun, etc.
- Message-ID: <2815@titccy.cc.titech.ac.jp>
- Date: 24 Jan 93 13:28:34 GMT
- References: <1993Jan17.000702.5794@Princeton.EDU> <1993Jan19.233642.18807@siemens.com>
- Sender: news@titccy.cc.titech.ac.jp
- Organization: Tokyo Institute of Technology
- Lines: 23
-
- In article <1993Jan19.233642.18807@siemens.com> aad@siemens.com (Anthony Datri) writes:
- >>(1) Is there any way to increase the size of a file partition from 2GB (to
- >>20 - 50 GB, for example) in Unix OS?
- >
- >On a typical machine, the filesystem calls (eg., fseek) take signed 32-bit
- >arguments -- hence the limit. To deal with bigger files/filesystems, you
- >need system calls that take bigger types as arguments.
-
- You don't have to. UNIX on PDP was using 16-bit arguments but
- files/filesystems can be as large as 32MB.
-
- >One way of doing this is to have a || set of calls that handle
- >64-bit offsets -- fseek64, say.
-
- Or, use 32 bit "seek()" (seek is an ancient system call).
-
- >Of course, this means that utilities have
- >to be modified to work.
-
- Interesting enough, you don't have to heavily modify existing file system
- utilities as they are originally coded with seek().
-
- Masataka Ohta
-