Sponsored Content
Operating Systems AIX AIX dump device not showing accurate size Post 303025987 by paqman on Friday 16th of November 2018 12:06:34 PM
Old 11-16-2018
Quote:
Originally Posted by bakunin
OK, this is a valid explanation. Still, i suggest you use smaller disks for your rootvg. In my experience it is best to put only filesystems really really belonging to the system (not the application, not the data, not anything else) into the rootvg. First, when you take a system backup you back up the rootvg, aka mksysb. Guess, how long that takes on a multi-terabyte rootvg and, bonus question, how big of a size the resulting mksysb-image will be. For reference, my largest database server (700G memory, ~80TB database) has a (2x, mirrored) 120GB rootvg - and this is only because the customers insisted on swap space that will never be used. Otherwise i would have gone with our 2x60GB-standard-rootvg.

Second, modern systems are usually virtual and the disks are too. There is a big difference in moving around system disks (controlled by VIOS) and non-system disks because these can be unmounted/varyoffed easily while the system is under load. Therefore it is a good idea to separate system- and non-system-disks into seaparate VGs.



First off: thank you for telling us that! I perhaps never would have had that idea at all and so i (and all the others reading this thread) learned something from here too. Absolutely commendable! A word of caution too: you shouldn't just overwrite parts of the system. AIX has a great packaging system and i suggest you use it to your advantage:

- check which package the file came from with
Code:
lslpp -w </path/to/file>

then replace this package with a newer version.

- if you are interested in which else files the package contains issue
Code:
lslpp -f <packagename>

to get a list of files/directories belonging to this package.

I hope this helps.

bakunin
Thanks! Yes, I agree this system should not have been installed on such large disks. There are a couple of 300GB disks in there that I think the rootvg should go on. I am new to this company and wasn't involved in installing the makesysb image. However, it is new and not in production yet, I may make the recommendation we move it to the other disks. Most of our systems do use virtual disk, however I think due to the particular function of this server they decided to install locally.

Thanks for the info about the packages, I will look into that! I have been a Unix/Linux SA for 15 years, but am very new to AIX, so I appreciate the advice.

------ Post updated at 10:06 AM ------

Just for some additional information, it looks like this problem existed on all the servers we had running AIX 7100-03-04-1441. The fileset for the dumpcheck script was bos.sysmgt.serv_aid 7.1.2.0.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

core dump file size

Hi All, is there any way to find out the optimal/would be size of the cor dump file generated by the system while a process got terminated abnormally? Basically we have been asked to provide the size of the core dump file being generated by the administrators who maintained the UNIX boxes.... (4 Replies)
Discussion started by: pushp.gahlot
4 Replies

2. UNIX for Advanced & Expert Users

Showing Device Does Not Exist While Taking Backup

Friends, while taking backup on /dev/rmt/0cn it is showing device does not exists. I have checked /dev/rmt 0cn is present there with link file created in /devices/pci@8,700000/scsi@5/st@5,0:cn I have checked cd /devices/pci@8,700000/scsi@5 but st@5,0:cn is not there. But I found st@3,0:cn. ... (3 Replies)
Discussion started by: ailnilanjan
3 Replies

3. AIX

The largest dump device is too small

1.what is dump device in AIX?... 2. i m getting this error message The largest dump device is too small. when i check the paging space , it is used only 41% any help welcome (4 Replies)
Discussion started by: click007
4 Replies

4. Shell Programming and Scripting

Shell Script not showing accurate Time Stamp and Size

Hey guys - I have made this script and for some reason, I dont see time stamp as "Month-Day-YYYY Hours-Mins" - all i see is Month and Day. Also, my file size is approximated. For example, if the size is 19,606KB - the script shows as 20M. Is there a way to see the exact file size? How do i... (2 Replies)
Discussion started by: DallasT
2 Replies

5. Solaris

iSCSI disk showing incorrect size

Hi, I have a very frustrating issue! I hope you guys can assist When a disk is presented out the iSCSI target display a lower disk capacity SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31 ISCSI Patch 119090-31, 141878-11 Unix Commands To discover Target bash-3.00# i... (0 Replies)
Discussion started by: capitalexall
0 Replies

6. AIX

The largest dump device is too small.

E87EF1BE 0605150011 P O dumpcheck The largest dump device is too small. bash-3.00$ errpt -aj E87EF1BE | more --------------------------------------------------------------------------- LABEL: DMPCHK_TOOSMALL IDENTIFIER: E87EF1BE Date/Time: Sun Jun 5 15:00:01... (4 Replies)
Discussion started by: thecobra151
4 Replies

7. AIX

change the primary dump device of a vio server

Hi how to change the primary dump device in a vio server ? $ ioslevel 2.2.0.11-FP-24 SP-01 $ oem_setup_env # sysdumpdev -l primary /dev/sysdumpnull secondary /dev/hd6 copy directory /var/adm/ras forced copy flag TRUE always allow dump TRUE dump... (1 Reply)
Discussion started by: newtoaixos
1 Replies

8. AIX

Dump device

Hi all I have a query about dump device in aix, i asked this question on interview. what is dump device, how to add dump device & its work. kindly give this answer, thanks in advance. :confused: (1 Reply)
Discussion started by: reply.ravi
1 Replies

9. Solaris

dedicated crash dump device

Hello Guys, I need a little help here. I have been studying crash dump and per what I am reading, you can dedicate a slice to use as a dump device. Now when you dedicate this slice, do you have to : 1) create a mount point? 2) add entry in /etc/vfstab? 3) is this slice wu or wm? 4) should... (3 Replies)
Discussion started by: cjashu
3 Replies

10. Solaris

Showing strange size in df output

Hi, This is Solaris-10 box and in few of file-system (root file-system of non global zones), usage/available is not showing correct size. I am not able to figure out, what is eating up this space. Global Server - bdrpod01 Non Global zone - bdrpod01-zputq01 root@bdrpod01:/root# df -h... (2 Replies)
Discussion started by: solaris_1977
2 Replies
vxpfto(1M)																vxpfto(1M)

NAME
vxpfto - set Powerfail Timeout (pfto) SYNOPSIS
vxpfto -g diskgroup -t timeout vxpfto [-g diskgroup] -t timeout volume_list vxpfto [-g diskgroup] -o pftostate={enabled|disabled} vxpfto [-g diskgroup] -o pftostate={enabled|disabled} volume_list DESCRIPTION
Powerfail Timeout is an attribute of a SCSI disk connected to an HP-UX host (see the pfto(7) man page). The vxpfto command sets the Power- fail Timeout interval on a set of Volume Manager disks, either all disks in a disk group, or all disks underlying the volumes listed. The first form of the command sets the same PFTO value for all the disks in the specified VxVM diskgroup. In the second form, all disks underlying the given list of volumes are selected, optionally restricted by the disk group specified with the -g option. If you specify a diskgroup, any volume in the list not belonging to the diskgroup is ignored. Use the -o pftostate option to disable or enable PFTO. By default, PFTO is enabled. You can enable PFTO either on all disks in a disk group, or on all disks underlying the volumes listed. If you invoke vxpfto without arguments, it displays a usage message. OPTIONS
-g diskgroup Specifies the disk group for the operation, either by disk group ID or by disk group name. -o pftostate={enabled|disabled} Enables or disables the use of PFTO for IO. -t timeout Specifies the PFTO value in seconds. The value must be zero or a positive integer. Zero represents the system default PFTO value. The default value depends on the disk driver controlling the disk device. volume_list A list of VxVM volume names. List items must be separated by white-space. EXIT CODES
vxpfto returns a zero if successful. If it encounters an error, vxpfto exits and displays a message on standard error. Defined exit codes are: 0 Success. 1 No PFTO value specified. 2 No diskgroup or volume list specified. 3 Illegal PFTO value specified. EXAMPLES
Set the PFTO value on all disks in disk group testdg to 100 seconds: vxpfto -t 100 -g testdg Set the PFTO value to 50 seconds on all disks underlying volume01 and volume02 in disk group testdg: vxpfto -t 50 -g testdg volume01 volume02 Set the PFTO value to 300 seconds on all disks underlying volume01 and volume02, even though they are not in the same disk group: vxpfto -t 300 volume01 volume02 Disable PFTO on all disks in disk group testdg: vxpfto -g testdg -o pftostate=disabled Enable PFTO on all disks underlying volume01 and volume02i in disk group testdg: vxpfto -g testdg -o pftostate=enabled volume01 volume02 SEE ALSO
vxdisk(1M), pfto(7) VxVM 5.0.31.1 24 Mar 2008 vxpfto(1M)
All times are GMT -4. The time now is 11:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy