Bug 27089

Critical

GemStone/S

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

All

OS network drives can confuse GemStone local/remote status

As of 6.0, GemStone no longer supports hosting extents, replicates,
or tranlogs on disk drives which are remote from the local machine
running the stone process.  Running with remote drives significantly
increases the complexity of the system and reduces performance over
a system using local drives.

GemStone normally detects remote drives, and will disallow any
operation attempting to use a remote drive for an extent, replicate,
or tranlog.  While GemStone currently does a good job in detecting
remote drives, unanticipated configurations and future enhancements
from OS vendors in the handling of network drives may potentially confuse
GemStone into thinking that a remote drive is instead local, and allow
the system to run with remote extents, replicates, and/or tranlogs.
Such configurations have not been QA tested by GemStone Systems, and
are unsupported.  Running with such a configuration could result in
system crashes and corrupted data.

Workaround

Be careful when configuring your system and make sure that all disk
drives used for extents, replicates, and tranlogs *really* are local
to the machine running the stone process.


Last updated: