Sponsored Content
Operating Systems Solaris Virtual disks are not showing up in LDom Post 302897073 by unblockable on Thursday 10th of April 2014 07:22:20 PM
Old 04-10-2014
Quote:
Originally Posted by Peasant
I see you are using slice0 of the disk.

You will need to specify the option for it :
Code:
ldm add-vdsdev options=slice /dev/dsk/c0t5000CCA015354CB4d0s0 vol5@primary-vds0

Or use the entire disk without the slice option :
Code:
ldm add-vdsdev /dev/dsk/c0t5000CCA015354CB4d0s2 vol5@primary-vds0

Hm I'm curious, is the options=slice required? Because I was able to add the first disk (or first slice rather?) successfully without it.

Quote:
I would also advice to create vds for every ldom, not use primary for everything.
Ah yes, this is probably good advice. I am a novice administrator, and I was just learning as I read the instructions. Moving forward I shall try to keep this in mind.

Quote:
The third disk with 'weird' partition table is actualy entire disk added (s2) and during the creation of the zpool inside of ldom no slice as used (c2d0 for instance).

This enables you to import the zpool on both architectures (x86 or sparc).
Ah, interesting. I wasn't aware of this, and I just used the format -e option to write an SMI label to disk to it matched the formatting of my other disks. I am not sure the purpose of this, I was simply trying to match the layout of my other disks...

After I labeled "c0t5000CCA0153596A4d0" with an SMI label, I was able to add slice 0 "c0t5000CCA0153596A4d0s0" as a virtual disk to my VM, and it showed up as a third disk. I am still unsure why my "c0t5000CCA0153542A4d0s0" did not show up properly as a virtual disk inside my VM, I will investigate later. But as for now it looks like my task is complete.

Thank you.
 

8 More Discussions You Might Find Interesting

1. Linux

LVM (volume manager) and virtual disks

:eek: Hi guys, I'm pulling my hair out over this one. I am trying to set up a virtual server environment. ( I am using VirtualBox, but I think this is irrelevant to this problem.) I have downloaded a pre-packaged Linux virtual disk, with which I have successfully started a virtual instance of a... (4 Replies)
Discussion started by: otheus
4 Replies

2. Solaris

How to create virtual disks in solaris

Hi, I have installed oracle 10g release 2 on solaris 10 Zone. I want to configure ASM in local Zone using virtual disks in place of real disks. I have configured ASM using virtual disks in place real disk in Solaris 10 Global zone. How i can do in local Zone Kindly guid me with proper... (1 Reply)
Discussion started by: malikshahid85
1 Replies

3. Solaris

Disks aren't showing up in Solaris/OBP

(Disclaimer: I put this in the "dummies" section because I am a UNIX noob and I'm not really sure what I'm doing so I felt like it belonged here. If it belongs in the Solaris section I can delete this and post it there:b:) I was handed over an Oracle SPARC T3-1 machine at work, with 8 physical... (15 Replies)
Discussion started by: bstring
15 Replies

4. Red Hat

Java process showing high virtual memory

Hi All, I have a java process which is showing high virtual memory utilization in client server. But the same process is showing comparitively lesser virtual memory consumption. I understand that virtual memory shown is not of much importance for the general user in normal condition, my client... (2 Replies)
Discussion started by: mritusmoi
2 Replies

5. Solaris

Virtual Switch in Solaris LDOM

Hi, Our existing environment is having primary domain and 3 guest domains are running over it. See the attached image. Now we want to add a new primary virtual switch and move LDOM3 to be connected with new primary switch. So, I am not sure how to achieve this because. If I remove the... (7 Replies)
Discussion started by: praveensharma21
7 Replies

6. Solaris

LDOM Solaris 11 add Network vsw (Virtual switch)

hello, I have a problem when configuring the network at the LDOM level, on a SPARC-Enterprise-T5120 machine The network goes through VLAN 503 (level, network tagget) And I need to give network to the guest domain: madarrwebsol10 I hope someone can bring some light .... Excuse my English ... ... (4 Replies)
Discussion started by: Wittman
4 Replies

7. Solaris

Missing ASM Disks in Solaris 11.3 LDOM

Hi Guys, Just a quick question hopefully someone will have seen this before and will be able to enlighten me. I have been doing some Infrastructure Verification Testing and one of the tests was booting the primary domain from alternate disks, this all went well - however on restarting one of... (7 Replies)
Discussion started by: gull04
7 Replies

8. Solaris

Virtual Terminal (Console) showing non-global zone?

Hope that everyone is doing well today. Happy Friday. I am running an illumos (opensolaris) based system which is like SmartOS, OmniOS, and OpenIndiana I have been searching all over the Internet into various documents and forms that have to do with Solaris, Opensolaris, Illumos, and SmartOS... (3 Replies)
Discussion started by: LonnieTC
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 05:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy