For data volumes, there is no 1 MB overhead.
You asked for 200 MB, and that is what you got!
200 MB * 1,048,576 Bytes/MB = 209,715,200 Bytes
Isn't this the amount of space it says it allocated?
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Malbrough, Demetrius" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
11/21/2001 09:26
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: dsmfmt question
It does require a 1MB overhead! e.g.
root@ / > dsmfmt -m -data /tsm/stgpool/backup1 200
AIX Server DSMFMT Extent/Volume Formatting Program Licensed Materials -
Property of IBM 5697-TSM (C) Copyright IBM Corporation 1990, 1997. All
rights reserved. U.S. Government Users Restricted Rights - Use,
duplication
or disclosure restricted by GSA ADP Schedule Contract with IBM
Corporation.
Allocated space for /tsm/stgpool/backup1: 209715200 bytes
Calculation:
200MB X 1024bytes = 204,800 bytes
204,800 bytes X 1024bytes =2.0971520 512-Blocks
Thanks,
Demetrius
-----Original Message-----
From: Mike Doneske [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 21, 2001 10:07 AM
To: [EMAIL PROTECTED]
Subject: Re: dsmfmt question
I just experienced this same problem this weekend when re-defining some
disk storage pools. I was using the DEFINE VOLUME command instead of the
DSMFMT utility. The command would fail but there would still be 408000
512-byte blocks left in the filesystem. The number of blocks left in the
filesystem seemed to be unrelated to the size of the volume I was trying
to
define as it failed at the same place on different size volumes. I would
also be interested in why TSM doesn't use every available block...
PAC Brion Arnaud
<arnaud.brion@PANA To: [EMAIL PROTECTED]
LPINA.COM> cc:
Sent by: "ADSM: Subject: Re: dsmfmt
question
Dist Stor Manager"
<[EMAIL PROTECTED]
EDU>
11/21/2001 09:31
AM
Please respond to
"ADSM: Dist Stor
Manager"
Hi Eric,
I re-read "TSM implementation guide" Redbook a couple of minutes ago,
and they don't speek about any overhead space for a data volume, what
they specify is that if you want to format a db volume, then the
allocated file size is always a multiple of 4 MB plus an additional 1 MB
for overhead.
Something else comes to my mind : when preparing your VG, did'nt you
forgot the "large file enable" parameter ?
Hope this helped, but probably somebody has a better knowledge than I
have ....
Cheers.
Arnaud
-----Original Message-----
From: Loon, E.J. van - SPLXM [mailto:[EMAIL PROTECTED]]
Sent: Mittwoch, 21. November 2001 15:54
To: [EMAIL PROTECTED]
Subject: dsmfmt question
Hi *SM-ers!
I will replace my 9 Gb. SSA disks in the very near future. The new disks
(36
Gb. 10.000 rpm) will have to be added to the diskpool one by one.
I remember from the last time that it was quite difficult to allocate a
disk
file which fills the disk completely. If you have, for instance, a 9 Gb.
disk, you cannot create a 9 Gb. file by issuing a DSMFMT -G -DATA
filename
9. This results in an error indicating the there isn't enough space
available. Apparently the dsmfmt utility needs a little bit overhead
space.
Does anybody know how to calculate the maximum space one can specify to
fill
the disk to it's maximum?
Thanks in advance for any reply!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee,
you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful.
If you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message. Koninklijke
Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees
shall not be liable for the incorrect or incomplete transmission of this
e-mail or any attachments, nor responsible for any delay in receipt.
**********************************************************************
