Sponsored Content
Operating Systems AIX Different sizes with getconf DISK_SIZE and lspv Post 302965786 by zaxxon on Wednesday 3rd of February 2016 04:58:36 AM
Old 02-03-2016
Different sizes with getconf DISK_SIZE and lspv

Hi all,

when I issue a lspv <hdisk>, I get
Code:
TOTAL PPs:          7199 (1842944 megabytes)

When I issue a getconf DISK_SIZE /dev/<hdisk>, I get
Code:
1048576

Where do those additional ~800 GB come from the output of lspv.. anyone an idea?

The volume is an EMC LUN provided by a VIOS and I have no access there.
Also I am not root so I cant check with bootinfo -s <hdisk>.

Thanks in advance!

cheers
zaxxon


EDIT:
I also did a check with lqueryvg -Atvp <hdisk> and got
Code:
Total PPs:      14398

Comparing the number of PP on the volume from lspv and the fact that the VG on this PV is placed on 2 hdisks of the same size, I assume that the output of lqueryvg is simly x2, ie. number of hdisks.
The VG on those 2 volumes is enhance-concurrent; maybe this counts in somehow too on some of the tools/outputs?

Also I got this Output, checking amount of PPs on the PV by VGID and PVID:
Code:
$ lquerypv -g 00caf4de00004c0000000137fe5de949 -p 00caf4deed67916b -n
1600


Last edited by zaxxon; 02-03-2016 at 06:30 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Directory sizes

Can someone tell me how to read these damn sizes. i mean, i prefer to see sizes in MB but that is not the case when you do an ls -l on directories. i have a had time converting these to MB just for verification purposes, what would a directory size like this = 3499990308 represent in MB or... (3 Replies)
Discussion started by: TRUEST
3 Replies

2. UNIX for Advanced & Expert Users

AIX p570 lspv, lslv etc... not working

Hi we are running a VIO server on a AIX p570 we cannot run and of the command the query the ODM has anyone seen this problem or has a solution the command just hangs. (1 Reply)
Discussion started by: truma1
1 Replies

3. Solaris

invalid getconf output and Perl compile

I was compiling perl on a Solaris 10 server. The compile failed because the output of getconf is wrong (it indicates xarch is generic64 not v9. This is a known bug but I cannot find a fix. I wrote a script as suggested that changes it but when you run getconf again it goes back to generic64. ... (2 Replies)
Discussion started by: csross
2 Replies

4. UNIX for Dummies Questions & Answers

getconf LONG_BIT and isainfo conflict

I wish to programmatically determine whether a solaris system is 32-bit or 64-bit. Investigation on the web suggested that the following commands were the right way to test this: # isainfo -kv # getconf LONG_BIT Strangely, on all three of the solaris systems I have access to, isainfo... (2 Replies)
Discussion started by: nosrednayduj
2 Replies

5. Shell Programming and Scripting

Awk command for search a string in lspv

I want to know wich hdisk have only one pvid and also display hdisk with two pvid. hdisk1 00c3fcd4e516183f testvg active hdisk2 00c3fcd4e516189b testvg active hdisk3 00c3fcd4e51618ec testvg ... (1 Reply)
Discussion started by: khalidou13
1 Replies

6. Shell Programming and Scripting

Awk command for search a string in lspv

I 've got this retourn when i tape the commande lspv: hdisk0 00c3fce454950416 rootvg active hdisk1 00c3fce454950416 rootvg active I want to verify if hdisk0 et hdisk1 have the same pvid (ex : 00c3fce454950416)? Can... (8 Replies)
Discussion started by: khalidou13
8 Replies

7. Shell Programming and Scripting

Help with file sizes

I have 2 big files in the size of gb. They are same with respect to content, both are “,” delimited. Now both of them are created by two different processes but has the same logic. The problem is they are differing only in few bytes for e.g one file is 202195751 bytes other is 202195773. So... (2 Replies)
Discussion started by: dsravan
2 Replies

8. AIX

Lspv -free command on VIOS

Hi all, When we run lpsv -free command on VIOS, it will take lot of time to display free disks i.e around 8 to 10 minutes. VIOS ioslevel is 2.2.1.4Can you have any solution for this problem? Many Thanks (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

9. AIX

Lspv -free command on VIOS

Hi all, We have observed that lspv -free command tooks 15 to 20 minutes to display the free disks and we have only 77 MPIO disks on VIO Server. Our VIOS version is 2.2.1.4. Please let us know what could be the reason that lspv -free command taking long time to display the output. Thank (4 Replies)
Discussion started by: m_raheelahmed
4 Replies

10. UNIX for Beginners Questions & Answers

Partition Sizes

Good Morning, What's a good way to get partition/slice sizes down to the byte on Solaris 9? I've tried a few ways, but only see results like 8.21GB which rounds the number. Thanks! (5 Replies)
Discussion started by: Stellaman1977
5 Replies
ICON(1) 						      General Commands Manual							   ICON(1)

NAME
icon - interpret or compile Icon programs SYNOPSIS
icont [ option ... ] file ... [ -x arg ... ] iconc [ option ... ] file ... [ -x arg ... ] DESCRIPTION
icont and iconc each convert an Icon source program into executable form. icont translates quickly and provides interpretive execution. iconc takes longer to compile but produces programs that execute faster. icont and iconc for the most part can be used interchangeably. This manual page describes both icont and iconc. Where there there are differences in usage between icont and iconc, these are noted. File Names: Files whose names end in .icn are assumed to be Icon source files. The .icn suffix may be omitted; if it is not present, it is supplied. The character - can be used to indicate an Icon source file given in standard input. Several source files can be given on the same command line; if so, they are combined to produce a single program. The name of the executable file is the base name of the first input file, formed by deleting the suffix, if present. stdin is used for source programs given in standard input. Processing: As noted in the synopsis above, icont and iconc accept options followed by file names, optionally followed by -x and arguments. If -x is given, the program is executed automatically and any following arguments are passed to it. icont: The processing performed by icont consists of two phases: translation and linking. During translation, each Icon source file is translated into an intermediate language called ucode. Two ucode files are produced for each source file, with base names from the source file and suffixes .u1 and .u2. During linking, the one or more pairs of ucode files are combined to produce a single icode file. The ucode files are deleted after the icode file is created. Processing by icont can be terminated after translation by the -c option. In this case, the ucode files are not deleted. The names of .u1 files from previous translations can be given on the icont command line. These files and the corresponding .u2 files are included in the linking phase after the translation of any source files. The suffix .u can be used in place of .u1; in this case the 1 is supplied auto- matically. Ucode files that are explicitly named are not deleted. iconc: The processing performed by iconc consists of two phases: code generation and compilation and linking. The code generation phase produces C code, consisting of a .c and a .h file, with the base name of the first source file. These files are then compiled and linked to produce an executable binary file. The C files normally are deleted after compilation and linking. Processing by iconc can be terminated after code generation by the -c option. In this case, the C files are not deleted. OPTIONS
The following options are recognized by icont and iconc: -c Stop after producing intermediate files and do not delete them. -e file Redirect standard error output to file. -f s Enable full string invocation. -o name Name the output file name. -s Suppress informative messages. Normally, both informative messages and error messages are sent to standard error output. -t Arrange for &trace to have an initial value of -1 when the program is executed and for iconc enable debugging features. -u Issue warning messages for undeclared identifiers in the program. -v i Set verbosity level of informative messages to i -E Direct the results of preprocessing to standard output and inhibit further processing. The following additional options are recognized by iconc: -f string Enable features as indicated by the letters in string: a all, equivalent to delns d enable debugging features: display(), name(), variable(), error trace back, and the effect of -f n (see below) e enable error conversion l enable large-integer arithmetic n produce code that keeps track of line numbers and file names in the source code s enable full string invocation -n string Disable specific optimizations. These are indicated by the letters in string: a all, equivalent to cest c control flow optimizations other than switch statement optimizations e expand operations in-line when reasonable (keywords are always put in-line) s optimize switch statements associated with operation invocations t type inference -p arg Pass arg on to the C compiler used by iconc -r path Use the run-time system at path, which must end with a slash. -C prg Have iconc use the C compiler given by prg ENVIRONMENT VARIABLES
When an Icon program is executed, several environment variables are examined to determine certain execution parameters. Values in paren- theses are the default values. BLKSIZE (500000) The initial size of the allocated block region, in bytes. COEXPSIZE (2000) The size, in words, of each co-expression block. DBLIST The location of data bases for iconc to search before the standard one. The value of DBLIST should be a blank-separated string of the form p1 p2 ... pn where the pi name directories. ICONCORE If set, a core dump is produced for error termination. ICONX The location of iconx, the executor for icode files, is built into an icode file when it is produced. This location can be overridden by setting the environment variable ICONX. If ICONX is set, its value is used in place of the location built into the icode file. IPATH The location of ucode files specified in link declarations for icont. IPATH is a blank-separated list of directories. The current directory is always searched first, regardless of the value of IPATH. LPATH The location of source files specified in preprocessor $include directives and in link declarations for iconc. LPATH is otherwise sim- ilar to IPATH. MSTKSIZE (10000) The size, in words, of the main interpreter stack for icont. NOERRBUF By default, &errout is buffered. If this variable is set, &errout is not buffered. QLSIZE (5000) The size, in bytes, of the region used for pointers to strings during garbage collection. STRSIZE (500000) The initial size of the string space, in bytes. TRACE The initial value of &trace. If this variable has a value, it overrides the translation-time -t option. FILES
icont Icon translator iconc Icon compiler iconx Icon executor SEE ALSO
The Icon Programming Language, Ralph E. Griswold and Madge T. Griswold, Prentice-Hall Inc., Englewood Cliffs, New Jersey, Second Edition, 1990. Version 9.1 of Icon, Ralph E. Griswold, Clinton L. Jeffery, and Gregg M. Townsend, IPD267, Department of Computer Science, The University of Arizona, 1995. Version 9 of the Icon Compiler, Ralph E. Griswold, IPD237, Department of Computer Science, The University of Arizona, 1995. icon_vt(1) LIMITATIONS AND BUGS
The icode files for the interpreter do not stand alone; the Icon run-time system (iconx) must be present. Stack overflow is checked using a heuristic that is not always effective. 1 November 1995 IPD244b ICON(1)
All times are GMT -4. The time now is 04:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy