Quantum

Software Product Bulletins and Alerts

StorNext Product Alerts

  • StorNext Product Alert #45 In rare cases, StorNext Storage Manager customers may encounter a Linux problem that can cause a duplicate data block. The problem is isolated to instances where a pse_snapshot is collected during a store to tape. No data is lost, but intervention is required to correctly retrieve the entire file and remove the duplicate block.
     
    Mar 2014
  • StorNext Product Alert #44 Before upgrading from a StorNext release prior to 4.2.2 to 4.2.2 or later, the file system may need a special cvfsck binary executed to repair some of the inodes.
     
    Aug 2013
  • StorNext Product Alert #43 cvcp does not verify the number of command line arguments, which can cause it to overwrite files if not used correctly.
     
    Aug 2013
  • StorNext Product Alert #42 After upgrading from Linter to MySQL, primary keys in database tables are missing.
     
    Mar 2013
  • StorNext Product Alert #41 Do not change or remove source replication policies in Storage Manager environments while files are being stored.
     
    May 2011
  • StorNext Product Alert #40 Storage Manager data unavailable starting January 1, 2012
     
    Apr 2011
  • StorNext Product Alert #39 Potential data integrity issues when defragmenting or migrating stub files
     
    Apr 2012
  • StorNext Product Alert #38 Sparc Solaris® StorNext clients can't mount volumes that are 1TB or larger
     
    Nov 2010
  • StorNext Product Alert #37 File replication to targets managed by Storage Manager may omit file data blocks
     
    Aug 2010
  • StorNext Product Alert #36 Possible data loss after snrestore -d
     
    Aug 2010
  • StorNext Product Alert #35 Possible data corruption with large metadata stripe group
     
    Oct 2010
  • StorNext Product Alert #34 A store policy time out may cause loss of some data stored on Storage Disk (sdisk) or Deduplicated Disk (ddisk, applicable to StorNext 3.x only).
     
    Apr 2010
  • StorNext Product Alert #33 A store policy is continuously started, causing the Linter database to use 75 - 80% of the available CPU cycles.
     
    Dec 2009
  • StorNext Product Alert #32 When the number of relation points for a file system exceeds the number of configured rebuild threads, files may not be placed on the store, truncation and relocation candidate list.
     
    Jun 2009
  • StorNext Product Alert #31 The new VTOC disk label format in StorNext 3.1.3 for Solaris 10 has implications for IRIX systems and backwards compatibility.
     
    Jun 2009
  • StorNext Product Alert #30 Changing target devices by adding or removing devices during active disk-to-tape writes stores without changing the OS mapping of the Stornext metadata controller can result in data corruption. Changes to the physical drive layout in the library must be reflected in the library configuration presented by the StorNext GUI.
     
    Apr 2009
  • StorNext Product Alert #29 Database corruption may occur if ha_redirect.conf is compromised by incomplete failover, manual edits, and/or control script edits. This Alert applies to Storage Manager installations that are HA enabled.
     
    May 2009
  • StorNext Product Alert #28 Data corruption may occur after bringing UP a stripe group that is marked DOWN.
     
    Jun 2009
  • StorNext Product Alert #27 Files stores can back up on a policy class if an fsrminfo command is done on media associated with the policy class.
     
    Mar 2009
  • StorNext Product Alert #26 A significant performance regression may be encountered when retrieving offline files from tape secondary storage. Retrieving files from storage disk is not impacted.
     
    Mar 2009
  •  
    Feb 2009
  • StorNext Product Alert #24 Allocation map inconsistency may occur on a stripe group that has gone through Bandwidth Expansion
     
    Feb 2009
  •  StorNext Product Alert #23 StorNext installations that utilize Deduplicated Storage Disk DDisk may encounter data corruption, and as a result blockpool data stored on the Sdisk may be inaccessible
     
    Feb 2009
  • StorNext Product Alert #22 The cvfsck command can report erroneous inconsistency that could result in data loss.
     
    Feb 2009
  • StorNext Product Alert #21 If StorNext receives a retryable tape drive error while fsmedcopy or fsfilecopy is executing, there is a chance during the retry process that tapes other than those being used for the fsmedcopy or fsfilecopy processes could be overwritten.
     
    Dec 2008
  • StorNext Product Alert #20 Possible data corruption due to Linux error handling
     
    Mar 2010
  • StorNext Product Alert #19 Possible data corruption
     
    Nov 2008
  • StorNext Product Alert #18 GUI may calculate the incorrect stripe breadth during file system expansion.
     
    Sep 2008
  • StorNext Product Alert #17 Possible metadata corruption
     
    Jun 2008
  • StorNext Product Alert #16 Possible loss of data on tape
     
    May 2010
  • StorNext Product Alert #15 Possible problems writing data to tape
     
    Apr 2008
  • StorNext Product Alert #13 Metadata on more than one stripe group can cause corruption
     
    Oct 2006
  • StorNext Product Alert #12 Possible data corruption when multiple data writes target a single file
     
    Jun 2006
  • StorNext Product Alert #11 Possible data corruption when accessing file systems using NFS and appending files that are under Storage Manager control
     
    Jun 2006
  • StorNext Product Alert #10 Possible data loss due to a hardware error or user intervention when a new tape is formatted and an active tape is in the drive
     
    Jun 2006
  • StorNext Product Alert #9 Expanding Stripe Group Bandwidth Using the Windows Configuration Administrator GUI will product incorrect file system configuration files causing data corruption
     
    May 2006
  • StorNext Product Alert #8 Possible data corruption when running Linux because the Linux sg_map utility rewinds mounted tape drives
     
    May 2006
  • StorNext Product Alert #7 Possible data corruption if raw devices are configured incorrectly
     
    Feb 2006
  • StorNext Product Alert #6 Running KUDZU on a Linux machine can cause data loss
     
    Dec 2005
  • StorNext File System Product Alert #4 Data corruption when writing sparse files for StorNext releases prior to 2.5
     
    Sep 2005
  • StorNext Product Alert #3 Possible data corruption when multiple extents are allocated for the same range in a file
     
    Nov 2004
  • StorNext Management Suite Product Alert #2 Alert for customers with journals exceeding 4MB in size
     
    Mar 2004
  • StorNext File System Product Alert #1 Alert for customers exporting the StorNext File System StorNext FS with multiple Network File System NFS clients
     
     
 

StorNext Product Bulletins

 

StorNext FX Product Alerts

  • StorNext FX Product Alert #12 Possible data corruption when multiple data writes target a single file
     
    Jun 2006
  • StorNext FX Product Alert #9 Expanding Stripe Group Bandwidth Using the Windows Configuration Administrator GUI will product incorrect file system configuration files causing data corruption
     
    May 2006
  • StorNext FX Product Alert #7 Possible data corruption if raw devices are configured incorrectly
     
    Feb 2006
 

StorNext FX Product Bulletins

 

AMASS for UNIX Alerts

 

AMASS for UNIX Bulletins

 

Vision Reporting Software Alerts

  • There are no Vision Reporting Software Alerts at this time
     
     
 

Vision Reporting Software Bulletins

  • There are no Vision Reporting Software Bulletins at this time