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 OSF1
advfsd
advfsd(8) System Manager's Manual advfsd(8)NAME
advfsd - Starts the AdvFS graphical user interface (GUI) daemon
SYNOPSIS
/usr/sbin/advfsd
DESCRIPTION
The AdvFS daemon, advfsd, is a process required by the AdvFS GUI (dtadvfs). The
advfsd daemon issues commands and obtains system information on behalf of the AdvFS GUI.
The /usr/var/advfs/daemon/socket/hosts.allow file contains a list of all hosts on which the advfsd daemon will allow the AdvFS GUI to run.
This file can be edited to add or remove hosts. Each host name must be on a separate line. For example:
host1
host3
host27
The /usr/var/advfs/daemon/socket/gui.passwd file, if it exists, is used by advfsd to force a dtadvfs user to enter a unique password when
attempting to connect to the host. The first line of this file is the unique password required by the GUI. For example:
guipassword
For security reasons, do not use the password of the root user or any other user; make up a unique name and do not encrypt it.
The advfsd daemon allows Simple Network Management Protocol (SNMP) clients such as NetView or Performance Manager (PM) to request AdvFS
file system information. SNMP clients cannot issue system configuration commands to the advfsd daemon.
The advfsd daemon is automatically started at boot time. Under normal conditions, this daemon does not need to be run manually.
If you do not want to have the daemon started at boot time, move the /sbin/rc3.d/s53advfsd file from its default location to another
directory and run it from that directory. Whenever you want to run the daemon at boot time, move the s53advfsd file back to the
/sbin/rc3.d directory.
The daemon (called an agent in the dtadvfs GUI interface) employs a file, /usr/var/advfs/daemon/disks.ignore, in which you can place the
names of disks that the daemon will ignore when it gathers information about disks on the system. If you use the disks.ignore file, you
can improve the performance of the dtadvfs GUI.
Each line in the disks.ignore file contains the name of a disk (with no directory partition letter) to be ignored by the daemon. For
example, to cause the disks /dev/disk/dsk3d and /dev/disk/dsk2g to be ignored, enter the following names on separate lines in the file:
dsk2
dsk3
You cannot ignore an LSM volume by including the LSM volume name in the disks.ignore file; you must list the disks from which the LSM vol-
ume is built. To ignore a complete disk group, you must list all the disks in it. Because all partitions on the listed disks will be
ignored, unexpected results may occur if a disk has partitions belonging to more than one disk group.
The disks.ignore file is processed each time the disks are checked. This means that if a disk fails or becomes unavailable, you can add the
disk name to the disks.ignore file and the daemon will ignore it. Once the disk is available, remove the entry from the file. There is no
need to stop the daemon.
For more information, see the GUI interface reference page , dtadvfs(8).
RESTRICTIONS
Only one advfsd daemon can be running on a system at a given time. If a second advfsd daemon attempts to start, it will fail.
You must be the root user to use this utility and you must register the Advanced File System Utilities license.
FILES
The script that starts the advfsd daemon at boot time. The advfsd message catalog. The SNMP data files. The sh scripts used by the dae-
mon to execute commands. The advfsd daemon executable. The advfsd daemon message log file. Remove or copy this log to another location
periodically to prevent the log from becoming too large. The security file that lists all hosts with permission to connect to the advfsd
daemon with the AdvFS GUI (dtadvfs). The advfsd password file. The file that lists all disks for the advfsd daemon to ignore when col-
lecting statistics about resources.
SEE ALSO advfs(4), dtadvfs(8)advfsd(8)