[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference star::wizards

Title: "ASK THE WIZARDS"
Moderator:QUARK::LIONEL
Created:Mon Oct 30 1995
Last Modified:Mon May 12 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1857
Total number of notes:3728

1528.0. "Open: problems with large files?" by STAR::JKEENAN () Tue Feb 11 1997 08:19

Return-Path: "VMS001::WWW"@vms001.das-x.dec.com
Received: by vmsmkt.zko.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
	Mon, 10 Feb 1997 16:46:57 -0500
Received: from vms001 by mail11.digital.com (8.7.5/UNX 1.5/1.0/WV)
	id QAA19491; Mon, 10 Feb 1997 16:35:40 -0500 (EST)
Date: Mon, 10 Feb 1997 16:36:19 -0500
Message-Id: <[email protected]>
From: "VMS001::WWW"@vms001.das-x.dec.com (10-Feb-1997 1636)
To: [email protected], [email protected], [email protected]
Subject: Ask the Wizard: '[email protected]'
X-VMS-To: [email protected]

Remote Host: (null)
Browser Type: Mozilla/2.02 (Win16; I)
Remote Info: <null>
Name: george caldwell
Email Address: [email protected]
CPU Architecture: VAX
Version: v 5.5-2
Questions: 

When checking files (out of and) into cms, large files,
on the order of 6500 blocks, give us a variety of symptoms.

Sometimes, cms says the files don't check in, but they do 
and are (show no reservations, and can be checked out), 
sometimes cms checks the files in, but saves 0 bytes!, 
sometimes we get the check in error, but the next try to
check in works fine.

The question is - with large files (6500 blocks +) are there
problems? With large files, could contention for system resources
cause this flakiness?

Are we the only ones with this problem? 

tia.

george
T.RTitleUserPersonal
Name
DateLines
1528.1If Running Recent CMS, Contact Digital SupportXDELTA::HOFFMANSteve, OpenVMS EngineeringTue Feb 11 1997 10:1821
   This appears to be a CMS problem, or a CMS library corruption.

   Please check the CMS version, and consider an upgrade.  CMS V3.8-2 is
   the current release.  (CMS V3.8-2 is known to have a problem retrieving
   indexed files from a CMS library.)

   Larger files -- particularly `binary' files such as Postscript, indexed
   files, image files, etc -- are not (locally) stored in CMS libraries as
   "delta" file elements... The "delta" of a `binary' file can be as large
   or larger than the source file itself -- CMS stores the "delta" in the
   library.

   Locally, a two-line `stub' -- called a "marker file" -- is stored in the
   CMS library, and this stub contains a reference to the actual file.  The
   storage and retrieval software knows how to recognize and process these
   marker files.

   If you are running a recent version of CMS, please contact Digital
   customer support for assistance.