>> Solaris also definitely does not support file sizes > 4GB and I would guess >> that there are even problems with a file size > 2 GB. > >Since Solaris 9 04/03 the supported max. file size is 16 TB. If an app >on solaris has problems wit h files bigger than 2GB or 4GB then because >either the app code itself limits the file size (becaus e the developer >once had the old limitations of older solaris ufs variants in mind) or >because the compiler (settings) when compiling the app for solaris still >set file size limits as if the app wo uld run on older solaris ufs versions.
The 2GB limit was lifted in Solaris 2.6 (not Solaris 9) and increased to whatever the underlying filesystem supports (for ufs this limit was approx 1TB until it was increased in the above mentioned S9 release) 64 bit apps deal with large file transparently; 32 bit apps need to be compiled with 64 bit file offsets (see lfcompile(5)) >To develope/compile an app that both limits files sizes correctly for >solaris 8 and on the other hand allows larger files on solaris 10, >then the app (its compiled binary) needs to know about (=check for) >the file system version it runs on. Or you need to compile version >specific binaries. Since Studio 11 allows you to compile performance >optimizations for solaris 10 and version-inspecific bi naries are >always bigger, I'ld always go the latter route. If you compile an application with the "large file compilation environment" in Solaris 2.6 or later, it will deal with large files correctly in 2.6 and later releases. The programs do not need to check the OS version once you've done that; any filesize limits which exists in the filesystem (such as the 4GB limit in pcfs) will be transparantly handled by the OS by returning an error once the limit for the underlying fs is reach. Solaris 2.6 was released late '97, so there's really no reason not to compile your apps to use 64 bit file offsets. Casper _______________________________________________ opensolaris-discuss mailing list [email protected]
