ADSM-L

virtual write error to RAID-1 *please ignore my last but one ma il with same concern - it splipped me away too early by an error*

2003-08-06 06:02:33
Subject: virtual write error to RAID-1 *please ignore my last but one ma il with same concern - it splipped me away too early by an error*
From: Salak Juraj <j.salak AT ASAMER DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 6 Aug 2003 12:03:21 +0200
Hello all,

I have an error I cannot pin down.

I have set reclaim of LTO to use a storage pool defined in SEQEUNTIAL FILE
device class.
This saves mount points in library and speeds reclamations things up at low
costs,
it is basically a recommendable configuration.

TSM sometimes gets a disk write error during such reclamation.
This happens not always, but quite often.

Till now everything sounds clear - I must have got either an HW or an
FileSystem problem.

BUT:
There is no evidence of a disk or file system related problem either in Raid
Controller or in Event Log.
Chkdsk reports no problems.

I am not able to provoke a simillar error using a test program even after
days of testing.

TSM uses same FileSystem for other operations, like of-bound Database
Backups and ExportNodes,
so the physical disk location where new files are created must steadily
change.
There are some heavily-used primary disk storage pools on the same disk
volume.

The write error seems to be limited to reclaim processes only.

The reclamation will usually work to a succesfull end,
because additional scratch volumes will be opened
and, if trillions of electorones decide so, written to end without a
failure.


Any ideas?
Maybe a known Bug in reclaim code?
Maybe an unknown bug in my mind?


best regards
Juraj Salak


Configuration:


2003.08.05 11:41:50      ANR1340I Scratch volume
V:\TSM\RECLAIMPOOL1\00000DAA.BFS
                          is now defined in storage pool RECLAIMTPDB.
2003.08.05 11:47:11      ANR9999D pvrfil64.c(1056): ThreadId<30> Error
writing FILE
                          volume V:\TSM\RECLAIMPOOL1\00000DAA.BFS.
2003.08.05 11:47:11      ANR1411W Access mode for volume
                          V:\TSM\RECLAIMPOOL1\00000DAA.BFS now set to
"read-only"
                          due to write error.

TSM Server 5.1.7.0
W2k US SP3
IBM x345 with two scsi  4M controllers
file system V:  is NTFS with 16 kB allocation unit (this is maybe the only
uncommon thing)
V: resides on an raid-1 drive


Reclamation process run for a tape volume from
               Storage Pool Name: TPDB
               Device Class Name: LTOCLASS
            Reclaim Storage Pool: RECLAIMTPDB
        ....

into reclaim pool
               Storage Pool Name: RECLAIMTPDB
               Storage Pool Type: Primary
               Device Class Name: RECLAIM1
               Next Storage Pool: TPDB
        ....

             Device Class Name: RECLAIM1
        Device Access Strategy: Sequential
            Storage Pool Count: 5
                   Device Type: FILE
                        Format: DRIVE
         Est/Max Capacity (MB): 5,120.0
                   Mount Limit: 6
                     Directory: V:\TSM\RECLAIMPOOL1

<Prev in Thread] Current Thread [Next in Thread>
  • virtual write error to RAID-1 *please ignore my last but one ma il with same concern - it splipped me away too early by an error*, Salak Juraj <=