|
From: Leigh O. <or...@ma...> - 2001-10-04 01:35:39
|
OK, I should have provided more information. This occurs with both Linux, kernel 2.4.10, using the filesystem Reiserfs (which allows for terrabyte sized files) and IRIX64 6.5 (the SGI Origin (modi4) at NCSA). This is not a filesystem problem. What I am calling modern hardware is what I just got for myself - a 1.4 GHz Athlon with 1 GB of memory. I do numerical modeling and lots of visualization/rendering - have been using vis5d since 1990 when I had to reserve time on a Stardent Stellar machine at SSEC where it was developed. A two-hour simulation with 6 variables, data every minute, on a ~ 100x100x60 grid can get big - and I am using a compression factor of 4 for accuracy. Can anyone tell me that they have created vis5d files which are larger than 2 GB successfully? The errors that go to stderr are of the "perhaps disk is full?" variety. Leigh Orf Glenn Carver wrote: | Leigh, | | You have probably hit a file size limit on the operating | system. Various unixes have a 2Gb limit on a single file | because this represents the maximum integer for a 32bit | operating system. This limitation is removed in 64bit | operating systems such as Sun's Solaris 8. | | Glenn Janko Hauser wrote: | Leigh Orf writes: | | > I've run into a problem creating large vis5d files, namely | > once a vis5d file hits 2 GB the routines to write it fail. | > | > Is this an integer overflow problem, or an inherent | > problem with the vis5d file format? Can it be easily | > fixed? With modern hardware I can easily visualize really | > big datasets and the 2 GB file size limit will become a | > real problem. | | Not only to help with your problem it would be quite | interesting, what you call modern hardware and also qhich OS | you are using. Or is everywhere hardware with more than 2Gb | of RAM in common use :-). If this is the case I have some | more arguments to get new hardware for the department. | | __Janko |