can't access new log volume

[JonRoenick]

I use 2 copies of my log files that are mirrored. This afternoon i attempted to extend my log file from 3GB to 5GB (each file is 1GB, so i'd be making a total of 4).

So i created the 4th GB file as /tsmlog01/log04.dsm and /tsmlogm01.dsm - and then i extended the log file. Q Log now shows up at 4GB.

However, i'm not sure what happened during the 5th GB but something isn't right. If i look inside AIX i can see /tsmlog01/log05.dsm and /tsmlogm01/logm05.dsm and they are using 1GB of diskspace. For whatever reason i can't make TSM see the mirrored copy (/tsmlogm01/logm05.dsm actually exists!). I get this error:

5/10/2010 3:37:31 PM ANR2441E DEFINE LOGCOPY: Volume /tsmlogm01/logm05.dsm is already defined as a recovery log volume.

5/10/2010 3:37:31 PM ANR0986I Process 99 for DEFINE LOGCOPY running in the BACKGROUND processed 1 items for a total of 1,049,624,576 bytes with a completion state of FAILURE at 15:37:31.

I don't want to extend the log until the mirror is synchronized but i don't know why the failure is happening.

 

[moon-buddy]

Was it sized properly?

 

[JonRoenick]

each file is formatsize=1000

 

[moon-buddy]

each file is formatsize=1000

Does the OS have enough space for the FS being created? The log space from the TSM prespective does not have a "look ahead" feature to determine if the FS has enough space.

 

[JonRoenick]

Yep, i have about 4GB available. I ended up just removing the 05.dsm files and starting over. The log extended so i seem to be ok <fingers crossed>