Sponsored Content
Operating Systems AIX rmdev won't remove disk device AIX Post 302378175 by filosophizer on Monday 7th of December 2009 06:24:21 AM
Old 12-07-2009
is there a volume group on hdisk495

can you please post here the output for

lsdev -Cc disk

lspv

lsvg


try to varyoff the volume group on hdisk495 then rmdev -Rdl hdisk495
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

available disk space on disk device???

Hello, Can someone please tell me which command to use to determine the available disk space on a given disk device? I have to write a shell script that compresses files and stores them in a specific location but I am not sure how "conservative" I should be? Thanks in advance! Al. (4 Replies)
Discussion started by: alan
4 Replies

2. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

3. HP-UX

Need to make disk device files match

Hi, I was wondering if there was a way to change the disk device files ex. /dev/dsk/cxtxd0 ? What I have are two HPUX 11.0 servers using MC Service Guard 11.13. A consultant attached a SAN and both servers had created the same identical LUN device files. Now I could begin creating my volume... (0 Replies)
Discussion started by: mvizza
0 Replies

4. OS X (Apple)

When a disk won't 'Unmount"

hdiutil detach -Force disk&number (ex:hdiutil detach -Force disk1) (3 Replies)
Discussion started by: unimachead
3 Replies

5. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

6. AIX

mkvg on iscsi disk won't work (6.1)

Hi All, Recently I'm taking my first steps in AIX, initially with no real issues. Until now, off course... I hooked up a couple of iSCSI disks to the system, with a RHEL5 machine running tgt on the other side. When running cfgmgr after initial configuration, I got an error: # cfgmgr -l... (4 Replies)
Discussion started by: mr.aart
4 Replies

7. Solaris

Determine free space in a Disk device

Version: Solaris 10 (August 2011) on VM I am kind of new to Solaris.From VM workstation i allocated 35 GB to this Solaris VM's Disk The disk was named c1t0d0 Few basic slices for root(8gb), swap(517mb) and /export/home(494mb) were created by the solaris Installer during the... (18 Replies)
Discussion started by: polavan
18 Replies

8. AIX

Clone or mirror your AIX OS larger disk to smaller disk ?

hello folks, I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies

9. Debian

Device error 71, won't mount root filesystem

I have a Debian OpenBox that boots from any usb port. The Debian LXDE will only boot from one specific port. It needs to look at all of them to find and be root, and mount the root filesystem by UUID. Both are full installs to 16GB flash drives. That is not being done. It says during boot... (0 Replies)
Discussion started by: patrick013
0 Replies

10. Linux

0: Failure: (138) Device does not have a disk-config

Hi guys, Any idea why I am getting the below error ? # drbdsetup disk-options 0 --resync-rate=500M 0: Failure: (138) Device does not have a disk-config Some info is; # fdisk -l Disk /dev/sda: 64.4 GB, 64424509440 bytes 64 heads, 32 sectors/track, 61440 cylinders Units =... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
VOS_ZAP(1)						       AFS Command Reference							VOS_ZAP(1)

NAME
vos_zap - Removes a volume from its site without writing to the VLDB SYNOPSIS
vos zap -server <machine name> -partition <partition name> -id <volume ID> [-force] [-backup] [-cell <cell name>] [-noauth] [-localauth] [-verbose] [-encrypt] [-noresolve] [-help] vos z -s <machine name> -p <partition name> -i <volume ID> [-f] [-b] [-c <cell name>] [-noa] [-l] [-v] [-e] [-nor] [-h] DESCRIPTION
The vos zap command removes the volume with the specified volume ID from the site defined by the -server and -partition arguments, without attempting to change the corresponding Volume Location Database (VLDB) entry. If removing the volume can possibly result in incorrect data in the VLDB, a warning message is displayed. The -force flag removes a volume even if it cannot be "attached" (brought online), which can happen either because the volume is extremely damaged or because the Salvager functioned abnormally. Without this flag, this command cannot remove volumes that are not attachable. See also CAUTIONS. To remove the specified read/write volume's backup version at the same time, include the -backup flag. CAUTIONS
Do not use this command as the standard way to remove a volume, as it is likely to put the VLDB out of sync with the volumes on servers. Use the vos remove command instead. This command is useful in situations where it is important to delete the volume, but for some reason the VLDB is unreachable -- for example, because the Volume Location Server is unavailable. The issuer can remove the VLDB entry later with the vos remove or vos delentry command, or it is removed automatically when the vos syncserv and vos syncvldb commands run. To remove a read-only site defined in the VLDB by mistake, before a copy actually exists at the site, use the vos remsite command. To remove an entire VLDB entry without affecting volumes at their sites, use the vos delentry command. Do not use the -force flag if the volume is online, but only when attempts to remove the volume with the vos remove or the vos zap command have failed, or the volume definitely cannot be attached. After using the -force flag, make sure that the volume's VLDB entry is also removed (issue the vos delentry command if necessary). Adding the -force flag makes the command take considerably longer -- about as long as a salvage of the relevant partition -- since the Volume Server examines all inodes on the partition for traces of the volume. OPTIONS
-server <server name> Identifies the file server machine from which to remove the volume. Provide the machine's IP address or its host name (either fully qualified or using an unambiguous abbreviation). For details, see vos(1). -partition <partition name> Identifies the partition (on the file server machine specified by the -server argument) from which to remove the volume. Provide the partition's complete name with preceding slash (for example, "/vicepa") or use one of the three acceptable abbreviated forms. For details, see vos(1). -id <volume ID> Specifies the volume ID number of the volume to remove, which can be of any of the three types. The volume name is not acceptable. -force Removes the volume even though it cannot be attached (brought online). Use only after the failure of previous attempts to remove the volume by using the vos remove command or the vos zap command without this flag. -backup Removes the backup version of the read/write volume specified by the -id argument. Do not use this flag if the -id argument identifies a read-only or backup volume. -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see vos(1). -noauth Assigns the unprivileged identity "anonymous" to the issuer. Do not combine this flag with the -localauth flag. For more details, see vos(1). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or -noauth flag. For more details, see vos(1). -verbose Produces on the standard output stream a detailed trace of the command's execution. If this argument is omitted, only warnings and error messages appear. -encrypt Encrypts the command so that the operation's results are not transmitted across the network in clear text. This option is available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. -noresolve Shows all servers as IP addresses instead of the DNS name. This is very useful when the server address is registered as 127.0.0.1 or when dealing with multi-homed servers. This option is available in OpenAFS versions 1.4.8 or later and 1.5.35 or later. -help Prints the online help for this command. All other valid options are ignored. EXAMPLES
The following example removes the volume with volume ID 536870988 from the /vicepf partition of the file server machine "fs6.abc.com", without noting the change in the VLDB. % vos zap -server fs6.abc.com -partition f -id 536870988 PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on the machine specified with the -server argument and on each database server machine. If the -localauth flag is included, the issuer must instead be logged on to a server machine as the local superuser "root". SEE ALSO
vos(1), vos_delentry(1), vos_remove(1), vos_remsite(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2014-04-08 VOS_ZAP(1)
All times are GMT -4. The time now is 01:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy