Sponsored Content
Operating Systems Solaris Exporting physical disk to ldom or ZFS volume Post 303016292 by psychocandy on Tuesday 24th of April 2018 04:37:26 AM
Old 04-24-2018
Quote:
Originally Posted by Peasant
In the second example, are you using ZVOLs ?

Using zvols is not so good performance wise.
You are adding additional layers without need.

If not, can you explain with a bit more detail how are you exporting mirrored zpool from primary to ldom ?

In the first example, you are doing things properly.

An output of the following commands would be useful :
Code:
ldm list -l <slow_perf_ldom>
ldm list-services

Yes ZVOLS....

We've managed to get rid of this now. Heres what we did:-

1. Added new LUN as vdisk to existing (exported zvol) on ldom as a mirrored disk. (Took a LONG time to resilver - which shows how slow the disk is).

2. Added another LUN as vdisk to create 3 way mirror (this was faster).

3. Dropped the old zvol from the mirror.

Performance is now MASSIVELY much faster.

Understand its not ideal to use the zvol but I can't see anything in manual which says its this bad.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

physical volume and physical disk.

Hello, I need explanations about physical disks and physical volumes. What is the difference between these 2 things? In fact, i am trying to understand what the AIX lspv2command does. Thank you in advance. (2 Replies)
Discussion started by: VeroL
2 Replies

2. UNIX for Dummies Questions & Answers

Physical volume- no free physical partitions

I was in smit, checking on disc space, etc. and it appears that one of our physical volumes that is part of a large volume group, has no free physical partitions. The server is running AIX 5.1. What would be the advisable step to take in this instance? (9 Replies)
Discussion started by: markper
9 Replies

3. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be... (1 Reply)
Discussion started by: chipahoys
1 Replies

4. HP-UX

Unmount and remove all Logical vol.Volume group and physical disk

Hi, Someone please help me with how i can unmount and remove all the files systems from a cluster. This is being shared by two servers that are active_standby. (3 Replies)
Discussion started by: joeli
3 Replies

5. Solaris

Ldom OS on SAN based zfs volume

Is it possible to use zvol from SAN LUN to install LDOM OS ? I 'm using following VDS from my service domain VDS NAME LDOM VOLUME DEVICE primary-vds0 primary iso sol-10-u6-ga1-sparc-dvd.iso cdrom ... (16 Replies)
Discussion started by: fugitive
16 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. Solaris

ZFS rpool physical disk move

I'd like to finish setting up this system and then move the secondary or primary disk to another system that is the exact same hardware. I've done things like this in the past with ufs and disk suite mirroring just fine. But I have yet to do it with a zfs root pool mirror. Are there any... (1 Reply)
Discussion started by: Metasin
1 Replies

8. Linux

Logical Volume to physical disk mapping

When installing Linux, I choose some default setting to use all the disk space. My server has a single internal 250Gb SCSI disk. By default the install appears to have created 3 logical volumes lv_root, lv_home and lv_swap. fdisk -l shows the following lab3.nms:/dev>fdisk -l Disk... (2 Replies)
Discussion started by: jimthompson
2 Replies

9. AIX

Trouble removing Physical Disk from Volume Group

I want to remove hdisk1 from volume group diskpool_4 and migrate PV from hdisk1 to hdisk2 , but facing problems, so what is the quickest way to migratepv and remove hdisk1 -- # lspv | grep diskpool_4 hdisk1 00c7780e2e21ec86 diskpool_4 active hdisk2 ... (2 Replies)
Discussion started by: filosophizer
2 Replies

10. Solaris

Sharing a physical disk with an LDOM

I have a guest LDOM running Solaris 10U11 on a Sun T4-1 host running Solaris 11.4. The host has a disk named bkpool that I'd like to share with the LDOM so both can read and write it. The host is hemlock, the guest is sol10. root@hemlock:~# zpool list NAME SIZE ALLOC FREE CAP DEDUP ... (3 Replies)
Discussion started by: Michele31416
3 Replies
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)
All times are GMT -4. The time now is 12:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy