When a disk is added to a VG it is sliced to pieces of PPsize. These pieces are then added to LVs, quasi one at a time.
Therefore, to find out how much space a disk in a vg provides you can calculate the number of PPs it provides times the size of one such PP.
If you want to know the raw disk size you could try the "size_in_mb" attribute in the device database. Not all disk types support this attribute, however. For example get the size of a 36GB SCSI disk used as "hdisk0":
You could also use the "bootinfo -s" command to get the diskspace. The results differ slightly from the output of "lsattr" because the one reports formatted and the other raw diskspace.
Hi
I'm trying to install gcc and the installation program tells me that I'm out of disk space! I have just installed the os (using the default settings for partitions and sizes) and have only installed apache on the machine. Can it really be out of disk space already?
How do I check how much... (4 Replies)
Hello,
Can someone please tell me which command to use to determine the available disk space on a given disk device?
I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be?
Thanks in advance!
Al. (4 Replies)
Hi
is there a cmd in hpux 11 to determine the physical size of the hard disk.
not bdf command.
i have searched the other threads here but cant find an answer.
thank you guys (4 Replies)
Hello All-
Am new member to this forum. Have some unix experience. But true believer in it compared to windows.
Have a question regarding the disk space.
I know a command to check the total disk space utilization using:
df -k .
but what is the command to check the same disk space by... (6 Replies)
Hi
I need to extend a FS in AIX but Im not sure on how to calculate the free space
Please advise if my math is correct:
-------PP SIZE: 64 megabyte(s)
--------TOTAL PPs: 1086 (69504 megabytes)
so the total size of volume is 64 * 1086 = 69504 MB (695GB)
Free PP is-- FREE... (4 Replies)
Hi,
I am new to shell scripting, and want to monitor disk space using shell script continously on server, which will shoot mail after crossing threshold limit
Please suggest.
Regards
Manoj (1 Reply)
Hi,
I have this :
uname -a
Linux servername 2.6.18-194.11.3.el5PAE #1 SMP Mon Aug 23 15:57:10 EDT 2010 i686 i686 i386 GNU/Linux
df -k
Sys. de fich. 1K-blocs Occupied Disponible Capacity Monted on
/u01/applis 10321208 3190160 6606760 33% /applis
Does it mean... (1 Reply)
Version: Solaris 10 (August 2011) on VM
I am kind of new to Solaris.From VM workstation i allocated 35 GB to this Solaris VM's Disk
The disk was named
c1t0d0
Few basic slices for root(8gb), swap(517mb) and /export/home(494mb) were created by the solaris Installer during the... (18 Replies)
Discussion started by: polavan
18 Replies
LEARN ABOUT V7
rp
RP(4) Kernel Interfaces Manual RP(4)NAME
rp - RP-11/RP03 moving-head disk
DESCRIPTION
The files rp0 ... rp7 refer to sections of RP disk drive 0. The files rp8 ... rp15 refer to drive 1 etc. This allows a large disk to be
broken up into more manageable pieces.
The origin and size of the pseudo-disks on each drive are as follows:
disk start length
0 0 81000
1 0 5000
2 5000 2000
3 7000 74000
4-7 unassigned
Thus rp0 covers the whole drive, while rp1, rp2, rp3 can serve usefully as a root, swap, and mounted user file system respectively.
The rp files access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk
records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A
single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are
transmitted. The names of the raw RP files begin with rrp and end with a number which selects the same disk section as the corresponding
rp file.
In raw I/O the buffer must begin on a word boundary.
FILES
/dev/rp?, /dev/rrp?
SEE ALSO hp(4)BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks.
Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples.
RP(4)