Sponsored Content
Full Discussion: update error
Top Forums UNIX for Dummies Questions & Answers update error Post 302261007 by seyiisq on Saturday 22nd of November 2008 09:06:45 PM
Old 11-22-2008
Quote:
Originally Posted by moshe fried
Hi,
Your problem is caused you don't have enough diskspace either where you are unpacking the package or in the temporary drive used by unzip. Check for a file system with enough disk space and check the option of unzip for a temporary work space.
If you still don't have enough either:
1) Remove what you can carefully.
2) Or add more disk space and unload there for temporary space.
(if you have windows professional you can export disks through NFS)
Moshe
I think this should be in my temp folder pls how do i increase the size of my temp folder
 

8 More Discussions You Might Find Interesting

1. SuSE

Error 15-the file was not found-update linux10.0 failure

I updated the Suse linux 10.0 OS online .The sysem ask me to reboot to take effects.I do so.But the OS do not load and show the message "Error 15 - The file was not found" What can I Do? It does not login to failesafe mode also.May I do reinstall the os through the cd ? Then HOW? I am Very New the... (0 Replies)
Discussion started by: nandhusky
0 Replies

2. Solaris

IPsec PF_KEY UPDATE error

Hello everyone :) First of all, happy new year. I am trying to set up an IPSec connection from a Solaris 10 Server to a Jetdirect 835n Printserver. We use certificates for the authentication (no preshared keys). The phase 1 completes succesffuly but the phase 2 doesn't. Unfortunately, I have no... (1 Reply)
Discussion started by: bonusk
1 Replies

3. Ubuntu

Can't update or use package manager -- gpg error

W: GPG error: http://archive.canonical.com karmic Release: Unknown error executing gpgv W: GPG error: http://us.archive.ubuntu.com karmic Release: Unknown error executing gpgv W: GPG error: http://us.archive.ubuntu.com karmic-updates Release: Unknown error executing gpgv W: GPG error:... (17 Replies)
Discussion started by: CRGreathouse
17 Replies

4. AIX

ML update error

Hi, I have servers JS21 with oslevel 6100-00-11-0943 and now I want to update it to 6100-01-02 but am getting an error. 0503-465 installp: The build date requisite check failed for fileset bos.rte.install. Installed fileset build date of 0943 is more recent than the selected fileset... (3 Replies)
Discussion started by: vjm
3 Replies

5. UNIX for Dummies Questions & Answers

error starting vim after an update?

After trying to make an update to my vim settings, i'm now getting this error message when vim tries to start. Any suggestions would be much appreciated :) Error detected while processing .vimrc: line 40: E15: Invalid expression: E15: Invalid expression: (0 Replies)
Discussion started by: khoges11
0 Replies

6. AIX

Update error - 7.1 migration builddate fail

Hi all, i have just migrate my aix 6.1 to 7.1. After migration my release is: 7100-00-03-1115 now i try to update to 7100-01-00-1140 but i receive lots of BUILD CHECK DATE FAILED on"mcr.rte" and other packets. +-----------------------------------------------------------------------------+ ... (3 Replies)
Discussion started by: Zio Bill
3 Replies

7. Red Hat

Cant update yum what so ever [Errno 14] HTTP Error 404 - Not Found

Hello!!! I am so frustrated I'm about to snap!!! I cant hear any sound in Firefox or re-install Chrome. Every time I try to do anything with YUM inside my terminal (like update or install) I keep getting this error:failure: repodata/repomd.xml from virtualbox: No more mirrors to try. I... (2 Replies)
Discussion started by: ApacheOmega
2 Replies

8. Fedora

Yum update error

Hello, I issued # yum update and received below error. Any idea? # yum update Loaded plugins: fastestmirror, universal-hooks Setting up Update Process Loading mirror speeds from cached hostfile * cpanel-addons-production-feed: 204.10.37.146 * base: mirrors.oit.uci.edu * extras:... (3 Replies)
Discussion started by: feroccimx
3 Replies
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)
All times are GMT -4. The time now is 06:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy