• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Discrepancy between Physical Space Occupied and Logical?

ldmwndletsm

ADSM.ORG Member
#1
I ran a `q occupancy nodename`, and everything matches exactly with the exception of two file spaces wherein the copy pool reports a larger number for Logical Space Occupied than the primary tape pool, but the number of files and physical space occupied are the same. There are no backups running, and no processes (e.g. migration or backup stgpool) that would apply, so everything is up to date.

Is this anything to be concerned about? Is this common? If so, is it any more likely on the primary versus the copy? Also, is the converse equally likely wherein the logical matches but not the physical?

Number_of_files Physical_space_occupied Logical_space_occupied
-------------------------------------------------------------------------
COPYPOOL 1,552,696 2,651,197.75 2,651,197.75
PRIMARY 1,552,696 2,651,197.75 2,650,923.00

COPYPOOL 5,008 72,606.63 72,606.63
PRIMARY 5,008 72,606.63 72,603.27
 

Trident

TSM noob with 12 years expirience
ADSM.ORG Moderator
#2
Hi,

From help q occ:

Physical Space Occupied (MB)
The amount of physical space that is occupied by the
file space. Physical space includes empty space within
aggregates, from which files might have been deleted or
expired. For this value, 1 MB = 1048576 bytes.

Tip: This field does not display a value for storage
pools that are set up for data deduplication. If you
turn off data deduplication for a storage pool, a value
for physical occupancy is not displayed until the
storage pool is empty of deduplicated files.

Logical Space Occupied (MB)
The amount of space that is occupied by logical files in
the file space. Logical space is the space that is
actually used to store files, excluding empty space
within aggregates. For this value, 1 MB = 1048576 bytes.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 18 18.6%
  • Keep using TSM for Spectrum Protect.

    Votes: 59 60.8%
  • Let's be formal and just say Spectrum Protect

    Votes: 12 12.4%
  • Other (please comement)

    Votes: 8 8.2%

Forum statistics

Threads
31,664
Messages
134,990
Members
21,691
Latest member
luciano91vs
Top