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
then replace this package with a newer version.
- if you are interested in which else files the package contains issue
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.
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)
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT HPUX
vxdiskadd
vxdiskadd(1M)vxdiskadd(1M)NAME
vxdiskadd - add one or more disks for use with Veritas Volume Manager
SYNOPSIS
vxdiskadd disk_address_pattern_list
DESCRIPTION
The vxdiskadd utility configures disks for use by Veritas Volume Manager (VxVM). Disks must already have been formatted. vxdiskadd
prompts the user for a disk group name and disk name for the disks. If no disk group name specified, the disks will be left as unassigned
replacement disks for future use. A new disk group may be created that will become the disks' disk group. If a disk group is specified for
the disks, the user is prompted for whether the disks should be designated as spares for the disk group. For new disks, all space on the
disk becomes free space in the disk's disk group. vxdiskadd interactively allows initialization to be done for all the disks specified or
allows the user to ask to make the decision for each disk individually.
One or more disks may be specified with a disk_address_pattern_list. The basic form of a disk address is c#t#d#. Any leading portion of
this address may be specified to indicate that all disks that match that leading portion should be used. For example c2t0 may be used to
specify all disks on controller 2, target 0. More than one disk address or address pattern may be specified on the command line. In case
of enclosure-based names, the disk address will be of the form enclosurename_diskno. The enclosurename indicates that all disks in the
specified enclosure are used. For example, emc1_ is used to specify all disks in the enclosure emc1. The word all may be used to specify
all disks on the system. Disk address names relate directly to device node names in the /dev/dmp and /dev/rdmp directories. Here are more
examples:
all: all disks
c3 c4t2: all disks on controller 3 and controller 4, target 2
c3t4d2: a single disk (in the c#t#d# naming scheme)
xyz_0 : a single disk (in the enclosure based naming scheme)
xyz_ : all disks on the enclosure whose name is xyz
The files /etc/vx/cntrls.exclude, /etc/vx/disks.exclude and /etc/vx/enclr.exclude may be used to exclude controllers or disks from use by
vxdiskadd. Each line of cntrls.exclude specifies the address of a controller to exclude, for example, c2. Each line of disks.exclude spec-
ifies a disk to exclude, for example, c0t3d0. Each line of enclr.exclude specifies the name of an enclosure to exclude, for example, enc0.
All courses of action that do not involve clear failure conditions require prompts from the user, with defaults supplied as appropriate.
Help is made available at every prompt. Entering ? in response to a prompt displays a context-sensitive help message.
OPERATIONS
Reconnecting a drive that was temporarily inaccessible
This situation is detected automatically by noting that the specified drive has a disk ID that matches a disk media record with no
currently associated physical disk. After reconnection, any stale plexes referring the disk are reattached, and any stopped volumes
referring the disk are restarted. This reattach action is performed by calling the vxrecover utility.
Initialization of a disk with reserved regions
Initialization of the disk is performed by calling vxdisksetup.
Adding a disk to an existing disk group
This operation can be performed independently of the initialization of the disk drive. The operation adds the disk to the group so
that its storage is added to the free space pool in that disk group. The vxassist utility can subsequently allocate from that free
space.
Creation of new disk groups in which to import a new disk
If disks are added that are required to be put into a disk group that does not exist, the option of creating the disk group is
offered.
Hardware-Specific Note
Some environments provide guidelines to optimize VxVM's interaction with intelligent storage systems. If these guidelines are present, VxVM
follows the guidelines when adding disks to disk groups. If the operation fails due to these guideline(s), you are prompted to use the
force option. The force option ignores any such storage-specific guidelines.
FILES
/etc/vx/cntrls.exclude Specifies the address of controllers to exclude from vxdiskadd operations.
/etc/vx/disks.exclude Specifies the address of disks to exclude from vxdiskadd operations.
/etc/vx/enclr.exclude Specifies the address of enclosures to exclude from vxdiskadd operations.
NOTES
EFI disks cannot be added to a disk group that is compatible with the Cross-platform Data Sharing (CDS) feature, nor can they be formatted
as CDS disks.
SEE ALSO vxassist(1M), vxdisk(1M), vxdiskadm(1M), vxdisksetup(1M), vxintro(1M), vxrecover(1M)VxVM 5.0.31.1 24 Mar 2008 vxdiskadd(1M)