Urgent: server down , lvmAddVol error on restart

2002-05-16 Thread chris rees

Hi ALL

In a bit of a pickle. TSM server has crashed as the log filled up.
The log size is 5196M.

I have dsmfmt another log file of 1024Mb and tried to do
dsmserv extend log /volumename 100
but get the dreaded lvmAddVol error.   I thought the limit was 5.5Gb hence
would have expected to be able to extend this.

any ideas

TIA

Chris

_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com



Re: Urgent: server down , lvmAddVol error on restart

2002-05-16 Thread David Longo

Delete you 1024 MB vol and dsmfmt another of about 400 MB and try 
again.  The linmit is somewhere around 5.5GB, don't remember
exact number.  This should get you out of jam.  Try 200MB if 400
fails.

David Longo

 [EMAIL PROTECTED] 05/16/02 01:56PM 
Hi ALL

In a bit of a pickle. TSM server has crashed as the log filled up.
The log size is 5196M.

I have dsmfmt another log file of 1024Mb and tried to do
dsmserv extend log /volumename 100
but get the dreaded lvmAddVol error.   I thought the limit was 5.5Gb hence
would have expected to be able to extend this.

any ideas

TIA

Chris

_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com 



MMS health-first.org made the following
 annotations on 05/16/02 14:17:25
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==



Re: Urgent: server down , lvmAddVol error on restart

2002-05-16 Thread Malbrough, Demetrius

This may help you a bit!!!

Problem Desc:  What are the maximum Database log LOG Logical Volume Sizes?

Solution:  The maximum Database log Logical Volume Sizes(*) are as follows:

Recovery Log: 5,704,253,440 bytes,
5,440 MB or
5.3125 GB

Data Base: 570,425,344,000 bytes,
544,000 MB or
531.25 GB.

Symptoms of exceeding:
ANRD adsmstart.c(2379): error=35 from LVMADDVOL

Refr: /lvm/lvm.h
#define LVMRC_MAX_LV_SIZE 35 /* Max Logical Vol size reached.*/

(*) These values are not affected by mirroring as mirrors do not affect the
logical volume size or the size of the LPT, Logical Partition Table. It is
the amount space reserved for storing the LPT in the check point area that
limits the logical volume size.

Another method to determine the maximum logical volume size is to use the
undocumented SHow LVMFA command. This is the preferred method as it is
possible that the maximum logical volume size may be changed in some future
version. The primary areas of interest are the output titled DB Logical
Partition Table area and LOG 1 Logical Partition area. The LOG 2...
section may be ignored as this area is for a design that was never
implemented.

adsm show lvmfa

LVM fixed storage area capacities:

Disk Table area:
14 pages allocated; 33 entries/page; 470 total entries.
Using an average disk name length of 37 characters.

Copy Table area:
6 pages allocated; 145 entries/page; 870 total entries.

DB Logical Partition Table area:
200 pages allocated; 679 entries/page; 135995 total entries;
Maximum possible DB LP Table size: 531.2 Gb.

LOG 1 Logical Partition Table area:
2 pages allocated; 677 entries/page; 1355 total entries;
Maximum possible LOG 1 LP Table size: 5.3 Gb.

LOG 2 Logical Partition Table area:
2 pages allocated; 677 entries/page; 1355 total entries;
Maximum possible LOG 2 LP Table size: 5.3 Gb

Regards,

Demetrius Malbrough
UNIX/TSM Administrator

-Original Message-
From: chris rees [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 16, 2002 12:56 PM
To: [EMAIL PROTECTED]
Subject: Urgent: server down , lvmAddVol error on restart


Hi ALL

In a bit of a pickle. TSM server has crashed as the log filled up.
The log size is 5196M.

I have dsmfmt another log file of 1024Mb and tried to do
dsmserv extend log /volumename 100
but get the dreaded lvmAddVol error.   I thought the limit was 5.5Gb hence
would have expected to be able to extend this.

any ideas

TIA

Chris

_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com



Re: Urgent: server down , lvmAddVol error on restart

2002-05-16 Thread Joel Fuhrman

If your server level is 4.1.x or lower then THE ABSOLUTE MAXIMUM SIZE OF A
LOG IS 5.3 gb.

On Thu, 16 May 2002, chris rees wrote:

 Hi ALL

 In a bit of a pickle. TSM server has crashed as the log filled up.
 The log size is 5196M.

 I have dsmfmt another log file of 1024Mb and tried to do
 dsmserv extend log /volumename 100
 but get the dreaded lvmAddVol error.   I thought the limit was 5.5Gb hence
 would have expected to be able to extend this.

 any ideas

 TIA

 Chris

 _
 Join the world s largest e-mail service with MSN Hotmail.
 http://www.hotmail.com