Dave,
On this system the disk partitioning is a little strange, there is only one
logical disk (a raid1) and one partition for os/db/archive log/active log.
8:51:45 spider : q log f=d
Total Space(MB): 16,384
Used Space(MB): 274
Free Space(MB): 16,030
Active Log Directory: /tsmdata0/activelog
Archive Log Directory: /tsmdata0/archivelog
Mirror Log Directory:
Archive Failover Log Directory: /tsmdata1/archivelog_overflow
spider:/proc # df -m
Filesystem 1M-blocks Used Available Use% Mounted on
/dev/sda1 839661 177359 662302 22% /
udev 8027 1 8027 1% /dev
/dev/sdb1 4766575 998071 3768504 21% /tsmdata1/filepool1
/dev/sdc1 4766695 1152537 3614158 25% /tsmdata1/filepool2
/dev/sdd1 4766575 1213984 3552591 26% /tsmdata1/filepool3
/dev/sde1 4766695 1085642 3681053 23% /tsmdata1/filepool4
spider:/proc #
-----Oorspronkelijk bericht-----
Van: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Namens Dave
Canan
Verzonden: maandag 19 juli 2010 20:53
Aan: ADSM-L AT VM.MARIST DOT EDU
Onderwerp: Re: [ADSM-L] nmon logging from Linux TSM 6.2.1.0 server
Stefan, can you also post the output from a 'q log f=d' command? I would
like to know the size and locations of your active log, archive log, and
failoverlog. Thanks
Dave Canan
IBM Advanced Technical Skills
ddcananATUSDOTIBMDOTCOM
On Mon, Jul 19, 2010 at 12:46 AM, Stefan Folkerts
<stefan.folkerts AT itaa DOT nl>wrote:
> I can't mail the nmon logging from the TSM server to the group because it's
> too large for the ADSM-L mailing list.
> Please send me an email if you want the file, I already send it to the two
> people requesting the file on this list.
>
> It's an quad core 3850 with 16GB memory.
>
> Cpuinfo ;
>
> spider:/proc # cat cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 15
> model name : Intel(R) Xeon(R) CPU 5150 @ 2.66GHz
> stepping : 6
> cpu MHz : 2656.000
> cache size : 4096 KB
> physical id : 0
> siblings : 2
> core id : 0
> cpu cores : 2
> fpu : yes
> fpu_exception : yes
> cpuid level : 10
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm
> constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr dca lahf_lm
> bogomips : 5324.61
> clflush size : 64
> cache_alignment : 64
> address sizes : 36 bits physical, 48 bits virtual
> power management:
>
> The system has a DS3K attached that is in use for FILE deviceclass
> storage, the tape library (an fc attached LTO4 TS3200) is only for creating
> copypool volumes.
> Dedupe is in use on the DS3K
>
> BTW, look at the dedupe, we got 70% reduction in data stored! :-)
>
> spider : q stgpool f=d
> Storage Pool Name: COPYPOOL
> Storage Pool Type: Copy
> Device Class Name: LTOCLASS
> Estimated Capacity: 119,254 G
> Space Trigger Util:
> Pct Util: 12.6
> Pct Migr:
> Pct Logical: 100.0
> High Mig Pct:
> Low Mig Pct:
> Migration Delay:
> Migration Continue:
> Migration Processes:
> Reclamation Processes: 1
> Next Storage Pool:
> Reclaim Storage Pool:
> Maximum Size Threshold:
> Access: Read/Write
> Description: Offsite copypool
> Overflow Location:
> Cache Migrated Files?:
> Collocate?: No
> Reclamation Threshold: 50
> Offsite Reclamation Limit: No Limit
> Maximum Scratch Volumes Allowed: 80
> Number of Scratch Volumes Used: 18
> Delay Period for Volume Reuse: 7 Day(s)
> Migration in Progress?:
> Amount Migrated (MB):
> Elapsed Migration Time (seconds):
> Reclamation in Progress?: No
> Last Update by (administrator): ADMIN
> Last Update Date/Time: 07/16/2010 07:14:25
> Storage Pool Data Format: Native
> Copy Storage Pool(s):
> Active Data Pool(s):
> Continue Copy on Error?:
> CRC Data: No
> Reclamation Type: Threshold
> Overwrite Data when Deleted:
> Deduplicate Data?: No
> Processes For Identifying Duplicates:
> Duplicate Data Not Stored:
> Auto-copy Mode:
> Contains Data Deduplicated by Client?: No
> Storage Pool Name: DISKPOOL
> Storage Pool Type: Primary
> Device Class Name: DISK
> Estimated Capacity: 0.0 M
> Space Trigger Util: 0.0
> Pct Util: 0.0
> Pct Migr: 0.0
> Pct Logical: 100.0
> High Mig Pct: 90
> Low Mig Pct: 70
> Migration Delay: 0
> Migration Continue: Yes
> Migration Processes: 1
> Reclamation Processes:
> Next Storage Pool:
> Reclaim Storage Pool:
> Maximum Size Threshold: No Limit
> Access: Read/Write
> Description: Diskpool
> Overflow Location:
> Cache Migrated Files?: No
> Collocate?:
> Reclamation Threshold:
> Offsite Reclamation Limit:
> Maximum Scratch Volumes Allowed:
> Number of Scratch Volumes Used:
> Delay Period for Volume Reuse:
> Migration in Progress?: No
> Amount Migrated (MB): 0.00
> Elapsed Migration Time (seconds): 0
> Reclamation in Progress?:
> Last Update by (administrator): ADMIN
> Last Update Date/Time: 06/03/2010 15:34:06
> Storage Pool Data Format: Native
> Copy Storage Pool(s):
> Active Data Pool(s):
> Continue Copy on Error?: Yes
> CRC Data: No
> Reclamation Type:
> Overwrite Data when Deleted:
> Deduplicate Data?: No
> Processes For Identifying Duplicates:
> Duplicate Data Not Stored:
> Auto-copy Mode: Client
> Contains Data Deduplicated by Client?: No
> Storage Pool Name: FILEPOOL
> Storage Pool Type: Primary
> Device Class Name: FILECLASS
> Estimated Capacity: 17,369 G
> Space Trigger Util: 91.1
> Pct Util: 26.4
> Pct Migr: 26.4
> Pct Logical: 79.3
> High Mig Pct: 90
> Low Mig Pct: 70
> Migration Delay: 0
> Migration Continue: Yes
> Migration Processes: 1
> Reclamation Processes: 4
> Next Storage Pool:
> Reclaim Storage Pool:
> Maximum Size Threshold: No Limit
> Access: Read/Write
> Description:
> Overflow Location:
> Cache Migrated Files?:
> Collocate?: No
> Reclamation Threshold: 20
> Offsite Reclamation Limit:
> Maximum Scratch Volumes Allowed: 850
> Number of Scratch Volumes Used: 248
> Delay Period for Volume Reuse: 0 Day(s)
> Migration in Progress?: No
> Amount Migrated (MB): 0.00
> Elapsed Migration Time (seconds): 0
> Reclamation in Progress?: Yes
> Last Update by (administrator): ADMIN
> Last Update Date/Time: 07/16/2010 07:14:25
> Storage Pool Data Format: Native
> Copy Storage Pool(s):
> Active Data Pool(s):
> Continue Copy on Error?: Yes
> CRC Data: No
> Reclamation Type: Threshold
> Overwrite Data when Deleted:
> Deduplicate Data?: Yes
> Processes For Identifying Duplicates: 2
> Duplicate Data Not Stored: 10,883 G (70%)
> Auto-copy Mode: Client
> Contains Data Deduplicated by Client?: No
>
> As said before, there are ~100 clients on this TSM server.
>
|
