AW: virtual write error on Raid-1

There is always some space left, 
lately about 16 GB, which is more than MAXCAP (5GB)
but less then MAXCAP times MOUNTLIMIT (5*6).

Neverthless, this was probably not the reason,
since scratch files created immediately afterwards by the very same 
reclaim process were written without problem.

thanks
Juraj



-----Ursprüngliche Nachricht-----
Von: Bill Boyer [mailto:bill.boyer AT VERIZON DOT NET]
Gesendet: Mittwoch, 06. August 2003 13:20
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: virtual write error on Raid-1


Is there space in the filesystem? The MAXCAPACITY of the device class...is
there that much space available?

Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Salak Juraj
Sent: Wednesday, August 06, 2003 5:30 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: virtual write error on Raid-1


Hello all,

anyone has seen before?

TSM Server reports sometiems write error on a disk raid-1 volume,
while
neither an evidence about an error is elsewhere (Raid-Controller, event log)
nor I am able to provoke an write error wit a test program.

This problem occures sometimes, but not always,
when an reclamation process reclaimss an LTO tape to a disk volume
defined in

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 5.1.7.0 on W2K SP3
IBM 345 with two Raid 4m controller, RAID-1 Disks