04-11-2014
Slice options is required if you are adding .. well slice.
You can add it without slice, but inside ldom you won't be able to use it as zpool vdev.
I personally like using slices, since it gives me much more flexibility. Slice with Solaris SVM for mirroring (if no external storage) and i use MD devices to add to LDOM(s)
Beware tho, Oracle Solaris 11.1 you must have 17.5 patchset if this to work.
They had the bug from 12.5 forward, which rendered SVM devices on slices unusable inside ldom (it didn't boot with strange messages in syslog).
Of course, because of SVM's great flexibility workaround was to break to mirror, boot from one mirror member, add another, and use mirroring inside ldom.
The downside of this is obvious, if an internal disk fails, you will need to replace and mirror inside every ldom that is using mirrored slices, instead of doing it centrally via SVM on control domain.
Hope that helps.
Regards
Peasant.
8 More Discussions You Might Find Interesting
1. Linux
: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
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
(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
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
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
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
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
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
LEARN ABOUT OSF1
volmirror
volmirror(8) System Manager's Manual volmirror(8)
NAME
volmirror - Mirrors volumes on a disk or control default mirroring
SYNOPSIS
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] medianame [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no] -a [new_medianame...]
/usr/sbin/volmirror [-g diskgroup] [-d yes|no]
/usr/sbin/volmirror [-g diskgroup] -D
OPTIONS
The volmirror command supports the following options: Limits operation of the command to the given disk group, as specified by disk group
ID or disk group name. The medianame operands will be evaluated relative to the given disk group. If no disk group is supplied to the
volmirror command, rootdg is presumed. Changes the default for subsequent volume creation, depending on the option argument. If the option
argument is yes, all subsequent volumes created using the volassist command will automatically be created as mirrored volumes. If the
option argument supplied is no, mirroring will be turned off for future volumes by default. Displays current default status for mirroring.
Mirrors all existing volumes for the specified disk group.
DESCRIPTION
The volmirror command provides a mechanism to mirror all the contents of a specified disk, to mirror all currently unmirrored volumes in
the specified disk group, or to change or display the current defaults for mirroring. All volumes that have only a single plex (mirror
copy), will be mirrored by adding an additional plex.
Volumes containing subdisks that reside on more than one disk will not be mirrored by volmirror.
The volmirror command is generally called from the voldiskadm menus. It is not an interactive command and once called, will continue until
completion of the operation or until a failure is detected.
Note
Due to the nature of generating mirror copies of volumes, this command may take a considerable time to complete.
In the first listed form of the command, the disk media name is supplied on the command line to volmirror. That name is taken to be the
only disk from which volumes should be mirrored. In the case of mirroring volumes from a specified disk, only simple single-subdisk volumes
are mirrored.
In the first and second listed forms of the command, the new_medianame ... parameter identifies a new disk media name (or set of names).
The mirroring operation being performed will use these names as targets on which to allocate the mirrors. An error will result if the same
disk is specified for both the source and target disk and if no other viable targets are supplied.
EXAMPLES
The following are examples of the use of the volmirror command. The following command mirrors the contents of the disk named disk01 to any
available space on any available disk. Subsequent calls to volassist will cause created volumes to be mirrored by default. volmirror -d
yes disk01 The following command displays the current status of default mirroring. It prints the string yes if mirroring is currently
enabled or no, if not. volmirror -D The following command mirrors any volumes on disk02 onto disk03. volmirror disk02 disk03
FILES
The defaults file for volassist parameters.
SEE ALSO
volintro(8), volassist(8), volrootmir(8)
volmirror(8)