|
|
Sponsored Content
Operating Systems
SCO
Swap space calculation
Post 302250845 by shamrock on Friday 24th of October 2008 12:00:30 PM
10-24-2008
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
All,
I am using SOLARIS 7. I have formated my hard drive to consist of only 150MB of swap space. This isn't enough considering I am running Oracle. How do I create additional swap space?
Please list sources or commands.
PS mkswap doesn't work on my machine. ( I have swap and... (5 Replies)
Discussion started by: SmartJuniorUnix
5 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I would like to know if there is any difference between the pageing space and the swap space.
Thank you in advance. (1 Reply)
Discussion started by: VeroL
1 Replies
3. AIX
how do you get the paging space reduced without rebooting the machine ? the os is aix (2 Replies)
Discussion started by: aaronh
2 Replies
4. UNIX for Dummies Questions & Answers
Plz I need to know how much swap mem free and used i have.
I'm using Compaq Tru64 UNIX V5.1A (rev 1885)
Thanx (1 Reply)
Discussion started by: Lestat
1 Replies
5. Linux
Hi,
I want to know how can i free the swap space if it is completely full,
0 mb remaining, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
6. Solaris
Could someone please explain how you know how much swap space you have on your system. See below:
# swap -s
total: 8225048k bytes allocated + 4863488k reserved = 13088536k used, 4008032k available
# swap -l
swapfile dev swaplo blocks free
/dev/dsk/c3t0d0s1 32,25 16... (2 Replies)
Discussion started by: jamba1
2 Replies
7. Linux
Hi,
i have done a blunder here, i increased the swap space on Xen5.6 server machine using below steps :-
1056 dd if=/dev/zero of=/root/myswapfile bs=1M count=1024
1057 ls -l /root/myswapfile
1058 chmod 600 /root/myswapfile
1059 mkswap /root/myswapfile
1060 swapon /root/myswapfile
... (1 Reply)
Discussion started by: apm
1 Replies
8. Solaris
Dear All,
I have a swap space of 16G available in Sol 10. I have allocated it as a seperate file system. But when the RAM Is full used , the system gets rebooted and the swap is not being used,.
Any reasons for this.
Rgds
Rj (5 Replies)
Discussion started by: jegaraman
5 Replies
9. Red Hat
CENT OS 5.8 server running with a huge java application which uses up all my ram (4GB) and requires excess of atleast 2GB.But the swap is not getting used up((8GB) of swap space left unused) leading a wierd error and stopping application to stop working.
Any one here dealt with the same kind of... (2 Replies)
Discussion started by: shiek.kaleem
2 Replies
10. UNIX for Advanced & Expert Users
I created a awk state to calculate the number of success however when the query runs it has a leading zero. Any ideas on how to remove the leading zero from the calculation?
Here is my query:
cat myfile.log | grep | awk '{print $2,$3,$7,$11,$15,$19,$23,$27,$31,$35($19/$15*100)}'
02:00:00... (1 Reply)
Discussion started by: bizomb
1 Replies
LEARN ABOUT HPUX
vparefiutil
vparefiutil(1M) vparefiutil(1M) NAME
vparefiutil - display, update, or delete HP-UX hardware path to EFI path mappings of bootable disks in the virtual partition database SYNOPSIS
db_file] hw_path] DESCRIPTION
The command displays the HP-UX hardware path to EFI path mappings that are stored in the virtual partition database. Legacy and agile hardware paths will be displayed, if available, as provided by HP-UX. If the virtual partition database is not specified, then the live database or by default is used. It can also be used to update the hw_path to EFI_path mappings from to the database. The behavior without any options is to display the HP-UX hardware path to EFI path mappings. This command is not supported on PA-RISC systems. Options and Arguments recognizes the following command line options and arguments: Specifies the alternate database from which the HP-UX hardware path to EFI path mappings need to be displayed, updated, or deleted. or live is default if this is not specified. Updates the database from the info available (from Displays the HP-UX hardware path to EFI path mapping in machine readable format. Each mapping is displayed in a separate line as follows: Deletes the HP-UX hardware path to EFI path mappings in the database. Note: In live database, this deletes only the HP-UX hardware paths owned by the vpar on which this command is executed. If this is specified, only the HP-UX hardware paths at or below the given hw_path are displayed, updated, or deleted. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. RETURN VALUE
returns the following values: Successful completion. Error condition occurred. EXAMPLES
Display the hw_path to EFI_path mappings from the live database. # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : 2.0.0.2.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : 2.0.0.3.0.6.0 EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : 2.0.0.3.1.2.0 EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(3|0)/Scsi(Pun6,Lun0)/ HD(Part1,Sig471031FC-6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.0.3.1.2.0 : EFI path : Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1kk0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Display the hw_path to EFI_path mappings from the alternate database in machine readable format. # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI::2.0.0.2.0.6.0 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI::2.0.0.3.0.6.0 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI::2.0.0.3.1.2.0 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: # vparefiutil -M -D vpdb_foo 2.0.0.2.0.6.0:Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI:: 2.0.0.3.0.6.0:Acpi(HWP0002,200)/Pci(3|0)/ Scsi(Pun6,Lkk6A12-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.0.3.1.2.0:Acpi(HWP0002,200)/Pci(3|1)/Scsi(Pun2,Lun0)/EFIHPUXHPUX.EFI:: 2.0.8.1.0.3.4.0.0.1.6:Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/ EFIHPUXHPUX.EFI::2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 2.0.12.1.0.4.1.8.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.10.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI:: 2.0.12.1.0.4.1.12.0:Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI:: Delete the HP-UX hardware-path paths to EFI path mappings at or below the HP-UX hardware path 2/0/0/3 of the current vpar. # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(PunA,Lun0)/ EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI # vparefiutil -d -H 2/0/0/3 # vparefiutil Hardware path - EFI path mapping ================================ Hardware path : 2.0.0.2.0.6.0 : EFI path : Acpi(HWP0002,200)/Pci(2|0)/Scsi(Pun6,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.8.1.0.3.4.0.0.1.6 : 2.0.8.1.0.0x50001fe1500339ed.0x1000000000000 EFI path : Acpi(HWP0002,28C)/Pci(1|0)/Pci(4|0)/ Fibre(WWN50001FE1500339ED,Lun1000000000000)/ HD(Part1,Sig9FEF4B40-6AC7-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.8.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/Scsi(Pun8,Lun0)/ HD(Part1,Sig00F95EE2-66C4-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.10.0 : EFI path : Acpi(HWP0002,2C6)/Pci(1|0)/Pci(4|1)/ Scsi(PunA,Lun0)/EFIHPUXHPUX.EFI Hardware path : 2.0.12.1.0.4.1.12.0 : EFI path pdb|0)/Pci(4|1)/Scsi(PunC,Lun0)/ HD(Part1,Sig4D70B9D6-6AD5-11D9-8002-D6217B60E588)/EFIHPUXHPUX.EFI For Serial Attach SCSI (SAS) devices, the SAS address is displayed along with the hardware path and the EFI path. Hardware path : 0.0.14.0.0.0.0.0.0.2.0 EFI path : Acpi(HPQ0002,PNP0A08,E)/Pci(0|0)/Pci(0|0)/ VenMsg(D487DDB4-008B-11D9-AFDC-001083FFCA4D)/ HD(Part1,SigC6B41C20-01BE-11DC-8000-D6217B60E588)/EFIHPUXHPUX.EFI SAS Address : 0x500000e01200d3f2 The SAS hardware path can potentially change from one OS instance to another, but the SAS address will remain the same. To locate SAS devices in different OS instances (for example, an nPar OS instance and a vPar OS instance), use the SAS address instead of the hardware path. WARNING
The option is provided only to remove the stale HP-UX hardware path to EFI path mappings. If you remove the valid HP-UX hardware path to EFI path mappings, you may not be able to load vpars. It is always better to follow the operation with a operation to update the database with the valid HP-UX hardware path to EFI path mappings available from AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), privileges(5), vparresources(5), vpartition(5), vpmon(5). Itanium(R)-Based Systems vparefiutil(1M)