Patch-ID# 113612-01
Keywords: 3.5 VERITAS ODM Rolling Patch for IR 138789, 139457
Synopsis: VERITAS Oracle Disk Manager 3.5 Maintenance Pack 2 Rolling Patch 1
Date: Jan/13/2004

Solaris Release: 2.8

SunOS release: 5.8

Unbundled Product: VERITAS ODM

Unbundled Release: 3.5

Topic: ODM 3.5 Maintenance Pack 2 Rolling Patch 1

Relevant Architectures: sparc

BugId's fixed with this patch: 

Changes incorporated in this version: 

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 

Obsoleted by: 

Files included with this patch:

/$ODM_ROOT_2.8/opt/VRTSodm/kernel/fs/odm
/$ODM_ROOT_2.8/opt/VRTSodm/kernel/fs/sparcv9/odm

Problem Description:

(138789) don't show ODM fid info as directory in /dev/odm/fid
(139457) Oracle dbw w/ odm on raw devices hangs in as_setprot during process exit

Patch Installation Instructions:
--------------------------------

For Solaris 2.0-2.6 releases, refer to the Install.info file and/or
the README within the patch for instructions on using the generic
''installpatch'' and ''backoutpatch'' scripts provided with each patch.

For Solaris 7-9 releases, refer to the man pages for instructions
on using ''patchadd'' and ''patchrm'' scripts provided with Solaris.
Any other special or non-generic installation instructions should be
described below as special instructions.  The following example
installs a patch to a standalone machine:
       
       example# patchadd /var/spool/patch/104945-02

The following example removes a patch from a standalone system:
       
       example# patchrm 104945-02

For additional examples please see the appropriate man pages.

Special Installation Instruction:
---------------------------------

This patch can only be applied to a system with
Veritas ODM 3.5 Maintenance Pack 2 installed.


Additional Notes:
-----------------

1) VERITAS Incident 138789

   The /dev/odm filesystem currently provides a 'fid' directory, where
   files that are currently identified by ODM show up as directory
   entries with their formatted FID as the filename.  This isn't a
   supported feature of ODM, but is intended as a debugging aid. 

   The presence of this directory seems to be causing substantial
   confusion among our customers and their applications.  More than one
   customer has been alarmed by the presence of large files in that
   directory ("do I have to back those up?"), not understanding that
   they're really just virtual files.  A recent escalation, 210-003-952,
   reports that Sun's SNMP library is choking when it finds >2GB files on
   the /dev filesystem.

   It seems that we are taking a significant support hit for providing
   this information in the form of a directory, without any significant
   benefit.  We could do one of

     1) provide the fid->file mapping information by having /dev/odm/fid
        be a character device that dumps out a list of mappings in text
        format

     2) remove /dev/odm/fid

   There seems to be consensus on the oraodm-dev list that no one really
   relies on the information in /dev/odm/fid, and that it can probably
   just be removed.

2) VERITAS Incident 139457

   Oracle dbw w/ odm on raw devices hangs in as_setprot during process exit

   The problem here is that the ioclean thread is deciding whether to
   clean up these i/o requests based on the odmio.unlck.len field.  The
   whole odmio structure is specific to vxfs and isn't used for raw
   files. 

   We already have a check in the vxfs-specific function
   odm_vx_iocleanup() for odmio.unlck.len == 0, so it would appear that
   the check in odm_ioclean() can be removed.