Sponsored Content
Operating Systems Solaris No local disk in format in Solaris Post 302777267 by solaris_1977 on Thursday 7th of March 2013 02:20:26 PM
Old 03-07-2013
format gives me long output of all Storage disks, but none of both local disks. Yes, disks are encapsulated with VxVM
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Finding local disk space

Hi Guys!! Iam new to this thread. I have a very urgent requirement of finding the local disk space. Iam running a php script on linux machine and need to find the local disk space on the remote machines. I tried using df -h, which works if I specify the drive name on the remote machine.... (4 Replies)
Discussion started by: navjak
4 Replies

2. Solaris

run xclock from local solaris to remote solaris

Hello - I am trying to connect to a remote solaris box from a solaris box i have locally present with me using 'ssh login@IP' ... Its connecting fine but... when I run xclock - it says 'Can't open display' Whereas, IF I connect to same remote solaris IP from my windows desktop locally via putty... (9 Replies)
Discussion started by: panchpan
9 Replies

3. Solaris

installing from local disk

We ordered a DVD for solaris 10 upgrade . However I realized that we have cd rom only and DVD is unreadable . Can i use this DVD , to upgrade the release from local disks. If yes , is there any specific procedure. (5 Replies)
Discussion started by: Hitesh Shah
5 Replies

4. UNIX for Advanced & Expert Users

Problems with tar between local and nfs disk

Hi, I am trying to move a local directory from a local disk to a nfs disk that has been shared on another file server. I am using this tar command: tar cf - . | (cd /export/nfsdisk && tar xpf - ) It copies the data okay but the big problem is that is resets the owner:group to 'nobody'. The... (2 Replies)
Discussion started by: jlowry
2 Replies

5. UNIX for Dummies Questions & Answers

Are disk format across AIX and Solaris platforms compatable?

I totally new to UNIX and I have a newbie question. I have 2 servers, AIX and Solaris and I need to be on just one platform. both serves have 2 physical drives, with the OS on one and data on the other. can I take the data drive from the AIX server and mount it on the Solaris server? or would... (2 Replies)
Discussion started by: AusTan24
2 Replies

6. Solaris

Sharing a local disk between to solaris machines

Hi, I recently added a disk on a solaris 9 and I wanted to make it accessible for another machine, using the same name here is what i did : On the machine holding the internal disk in vfstab i added the line /dev/dsk/c1t1d0s4 /dev/rdsk/c1t1d0s4 /SHARED2 ufs 2 yes ... (2 Replies)
Discussion started by: zionassedo
2 Replies

7. AIX

Sysdump on local disk

Hello Team, Our p740 systems are booting up from SAN. We would like to configure the local disk(which is not part of rootvg) as a primary dump device. I have assigned the same too. But in the errpt throwing the below error. Please help me on this. ... (1 Reply)
Discussion started by: gowthamakanthan
1 Replies

8. Shell Programming and Scripting

Unable to convert passwd lastupdate value into scalar local format

Dear all, I am unable to get the desired result upon executing the below script. the problem is at `perl -le 'print scalar localtime $msecage'` ouput which gives the following result "Thu Jan 1 05:00:00 1970" instead of "Tue Nov 13 10:30:56 2012" but when I run the same command from shell... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies

9. UNIX for Beginners Questions & Answers

SAN vs. Local disk.

I am in the market looking to purchase a new E950 server and I am trying to decide between using local SSD drives or SSD based SAN. The application that will be running on this server is read-intensive so I am looking for the most optimal configuration to support this application. There are no... (2 Replies)
Discussion started by: ikx
2 Replies
voldiskadd(8)						      System Manager's Manual						     voldiskadd(8)

NAME
voldiskadd - Adds one or more disks for use with the Logical Storage Manager SYNOPSIS
/usr/sbin/voldiskadd disk-address-list DESCRIPTION
The voldiskadd utility sets up new disks that are added to the system after the initial system installation and configures the disks for use by the Logical Storage Manager. A valid disk label must exist on the disk before using the voldiskadd utility. One or more disks may be specified using a disk-address-list. Disk addresses in the list have the form dskn (for the entire disk) or dsknp (for a specific partition). When specifying multiple disks, use a space between entries. Disk address names relate directly to device names in the /dev/disk directory. For example, here are some valid voldiskadd disk-address-list specifications: # voldiskadd dsk1 # voldiskadd dsk2 dsk3a The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadd. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadd utility prompts the user for a disk group name and disk media name for the disks. If a new disk group name is specified, that disk group is created for the new disks. If no disk group name is specified, the disks are left as unassigned replacement disks for future use. If an existing disk group name is specified, the user is prompted for whether the disks should be designated as spares for the disk group. If a disk is found to already contain non-Logical Storage Manager partitioning, the user is asked whether the disk should be encapsulated. Encapsulation turns each partition of the disk into a volume. A disk should be encapsulated if it contains file systems or data that should not be overwritten. If encapsulation is not desired for a disk, the disk can be initialized as a new disk for use by the Logical Storage Manager. For new disks, all space on the disk becomes free space in the disk's disk group. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. The voldiskadd utility supports the following general classes of actions: Initializing a disk with reserved regions and partitions. Disk initialization is performed by calling voldisksetup command. Adding a disk to an existing disk group. This operation can be performed independently of the initialization of the disk drive to add a disk's storage space to a disk group's free space pool. The volassist command may subsequently allocate from that free space. The disk can also be added as a hot spare device. Creating new disk groups in which to import new disks. If no disk group exists for importing disks, the option of creating the disk group is offered. Encapsulating disks that have exist- ing contents. This is the default action for disks that do not have a valid, existing Logical Storage Manager private region, but that do have a disk label. Encapsulation is performed by calling volencap. 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 volrecover script. ERRORS
You may receive the following messages when using the voldiskadd command: Initialization of disk device special-device failed. Error: special-device or an overlapping partition is open. This message indicates that the partition you specified or an overlapping partition on the disk is actively in use. The partition could be a mounted UFS or AdvFS filesystem, initialized as an LSM disk or used as a swap device. special-device is marked in use for fstype in the disklabel. If you continue with the operation you can possibly destroy existing data. Would you like to continue?? [y,n,q,?] (default: n) This message indicates that the fstype of a partition or an overlapping partition is set in the disk label. The voldiskadd command prints this message to warn that a disk partition may have valid data which could be destroyed. If you are sure that the disk partition does not have valid data and that the partition can be added to LSM, you can ignore the warning message by entering y at the prompt. The voldiskadd command will proceed to initialize the disk partition and add it to LSM. FILES
A list of disks to exclude from use by voldiskadd. SEE ALSO
disklabel(8), volassist(8), voldisk(8), voldiskadm(8), voldisksetup(8), voldg(8), volintro(8) voldiskadd(8)
All times are GMT -4. The time now is 11:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy