if you do this on ASM disks or gpfs disks you are wiping the header. The device will stay up til your next reboot and be beautiful and clean after the reboot so this is a terrible idea.
You do get an output from the commands I listed even with ASM devices and GPFS disks and even from completely unassigned open disks. It might be a cryptic unreadable output but it is an output. If you get nothing or a one-line-error the disks are not open.
But maybe I have a different understanding what open means. Are you trying to find out if the disks are unused? Are you using AIX mpio or any kind of multipathing software? With ASM, before you make ANY changes to the disks, ask the DBAs to backup the disk headers. Strictly speaking by design, AIX has no idea if the disks are used or not - but oracle will hold a lock on them while still allocated - which is a curse and a blessing for above reason - you will STILL wipe the header. For gpfs, the cluster itself should be able to tell you which disks it is using - try
command. For normal disks in VGs, a simple
will tell you which disks are not in use from LVM perspective.
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440.
after... (3 Replies)
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 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)