Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Roedy Green Newsgroups: comp.lang.java.programmer Subject: Re: Is there a file limit size of 2GB in JDK 1.5 Date: Fri, 16 Sep 2011 14:28:55 -0700 Organization: Canadian Mind Products Lines: 25 Message-ID: References: Reply-To: Roedy Green NNTP-Posting-Host: RCd/Ul4tyxGUBII8WGwa5g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Forte Agent 6.00/32.1186 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:8088 On Fri, 16 Sep 2011 12:18:16 -0700 (PDT), zigzagdna wrote, quoted or indirectly quoted someone who said : >It cannot be HP UNIX limitation which is 64 bit, also file systems >have been set to allow files larger than 2GB. I am surprise that >java's i/o is 32 bit (yes java's version is most likely 32 bit). hmm. Java itself uses longs (64 bits) for file offsets. There is some native code that java.io. uses to hook into the OS. It might be designed for an older 32-bit HP API. Or it may be that partitions are old, 32-bit even under the new 64-bit os. You may have to reformat them to free up 64 bit power. Try an experiment with C to see if it too has this limit on that partition. Consider that Java 1.5 has been declared obsolete for quite some time now. JDK 1.7 is out. Try your code with 1.7 and see how it works. -- Roedy Green Canadian Mind Products http://mindprod.com Your top priority should be fixing bugs. If you carry on development, you are just creating more places you will have to search for them.