Sponsored Content
Operating Systems Solaris Remove old subpaths from vxvm/format/cfgadm Post 302514795 by masloff on Monday 18th of April 2011 05:28:55 AM
Old 04-18-2011
Hmm, this is a prod system, so I`m not very sure I can run mentioned commands without minor outages.

Is restarting of vxconfigd safe? Also, restarting of it will remove devnodes from /dev ?
 

10 More Discussions You Might Find Interesting

1. Solaris

VxVM

All solaris rescue gurus out there .... I've a Solaris 2.6 E450 on which my sysadmin guy has deleted every file (not sub-directories) from the /etc directory. The machine is (was) running Vxvm with the root volume encapsulated. I've tried booting from CDROM, mounting the root volume... (3 Replies)
Discussion started by: andy11983
3 Replies

2. Solaris

VxVM softpartitions

Is there a way to create "softpartitions" with Veritas Volume Manager? I have a bunch of disks and i want to create a RAID 5 with them. On that RAID5, i want to split that RAID into two separated file systems like i could do it with SDS/LVM or ZFS, but i don't want to create two RAID5 in the... (3 Replies)
Discussion started by: pressy
3 Replies

3. Solaris

unconfigure using cfgadm

Hi, One of 2 local disks on V480 running solaris 10 and SVM failed. Now after running metadettach for submirrors on that disk, I want to unconfigure the FAULTY disk using cfgadm -c uncofigure command..and then put new one and configure that. but surprisingly I don't see local dsk in cfgadm... (17 Replies)
Discussion started by: upengan78
17 Replies

4. Solaris

cfgadm - is this an error?

# cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 CD-ROM connected configured unknown c1 scsi-bus ... (8 Replies)
Discussion started by: robsonde
8 Replies

5. Solaris

Issue with cfgadm

I have an issue with on T3-Lun where Veritas dont like it anymore and OS-system have issues with it too. So I thought to unconfigure it but even that does not work cfgadm -al | grep c17 c17::50020f230000eae0 disk connected unconfigured unkown then I tried a cfgadm -c unconfigure... (2 Replies)
Discussion started by: manni2
2 Replies

6. Solaris

vxvm

hi all, how can we check whether vxvm is installed in our system or not in solaris? Thanks in advance dinu (4 Replies)
Discussion started by: dinu
4 Replies

7. Solaris

Hot swapping disks on V240 - blue light not lit after cfgadm -c unconfigure

Hot swapping a drive on V240. So, I do cfgadm -c unconfigure <disk>. Then cfgadm -al reports disk as unconfigured as expected. format then tells me there is no disk. BUT, blue light does not come on. Done the exact same command on my V440 and blue light does come on. V240 Server Admin... (0 Replies)
Discussion started by: psychocandy
0 Replies

8. Emergency UNIX and Linux Support

VxVM not able to see new disk

I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list". I already tried commands --> vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies

9. Solaris

Fsck in vxvm

Hi, When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also. compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS. Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies

10. AIX

VXVM in POWERHA 6.1

I have created a VxVM disk group in AIX7.1. I have tried to added this VxVM disk group in powerHA 6.1. But in cluster VxVM DGs are not listing. Is there any other procedure to add vxvm diskgroup to hacmp. Please share me steps for adding vxvm diskgroup to hacmp. (6 Replies)
Discussion started by: sunnybee
6 Replies
REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME
reboot, poweroff, halt -- restarting, powering down and stopping the system SYNOPSIS
halt [-dlnpqvxz] poweroff [-dlnqvxz] reboot [-dlnqvxz] [arg ...] DESCRIPTION
The poweroff, halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM, wait for up to 30 seconds for them to die, send a SIGKILL to the survivors and, respectively, power down, halt or restart the system. The action is logged, including entering a shutdown record into the login accounting file and sending a message via syslog(3). The options are as follows: -d Create a dump before halting or restarting. This option is useful for debugging system dump procedures or capturing the state of a corrupted or misbehaving system. -l Suppress sending a message via syslog(3) before halting or restarting. -n Do not flush the file system cache. This option should be used with extreme caution. It can be used if a disk or a processor is on fire. -p Attempt to powerdown the system. If the powerdown fails, or the system does not support software powerdown, the system will halt. This option is only valid for halt. -v To enable verbose messages on the console, pass the boothowto(9) flag AB_VERBOSE to reboot(2). -x To enable debugging messages on the console, pass the boothowto(9) flag AB_DEBUG to reboot(2). -z To silence some shutdown messages on the console, pass the boothowto(9) flag AB_SILENT to reboot(2). -q Do not give processes a chance to shut down before halting or restarting. This option should not normally be used. If there are any arguments passed to reboot they are concatenated with spaces and passed as bootstr to the reboot(2) system call. The string is passed to the firmware on platforms that support it. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom. SEE ALSO
reboot(2), syslog(3), utmp(5), boot(8), init(8), rescue(8), shutdown(8), sync(8) HISTORY
A reboot command appeared in Version 6 AT&T UNIX. The poweroff command first appeared in NetBSD 1.5. CAVEATS
Once the command has begun its work, stopping it before it completes will probably result in a system so crippled it must be physically reset. To prevent premature termination, the command blocks many signals early in its execution. However, nothing can defend against delib- erate attempts to evade this. This command will stop the system without running any shutdown(8) scripts. Amongst other things, this means that swapping will not be dis- abled so that raid(4) can shutdown cleanly. You should normally use shutdown(8) unless you are running in single user mode. BUGS
The single user shell will ignore the SIGTERM signal. To avoid waiting for the timeout when rebooting or halting from the single user shell, you have to exec reboot or exec halt. BSD
February 16, 2011 BSD
All times are GMT -4. The time now is 10:49 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy