Bug 30202

Bug: 30202

Impact:

Product:

GemStone/S

Versions:

6.7.2.1, 6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.2, 6.0.1, 6.0

Platform:

Unix

Fixed In:

GsFile doesn't use 64 bit file I/O

The GemStone Smalltalk class GsFile does not use 64 bit system file
I/O, so GsFile operations on files larger than 2 GB will fail.

In most cases, the failure will manifest itself as methods returning
nil, such as when trying to open or get the status of a file
(GsFile>>openReadOnServer:, GsFile>>sizeOf:  or
GsFile>>exists:onServer:).

On Linux, trying to write a file beyond the 2 GB boundary will cause
the gem process to dump core.

This bug only applies to GsFile. GemStone properly handles large
database files (tranlog, extent and backup files).

Workaround

Use System(C)>>performOnServer: to invoke operating system shell
commands to check status of large files. Do not attempt to write
large files with GsFile.