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
vxbrk_rootmir(1M)														 vxbrk_rootmir(1M)

NAME
vxbrk_rootmir - break off a mirror of a VxVM root disk to create a separate root disk generation SYNOPSIS
/etc/vx/bin/vxbrk_rootmir [-g diskgroup] [-v] [-b] [-t tasktag] {daname|dmname} DESCRIPTION
The vxbrk_rootmir command creates a mirror of a Veritas Volume Manager (VxVM) rootable boot disk, breaks the mirror, and then makes the broken-off mirror into a completely separate root disk that is suitable for booting by itself. Except the specified target disk, the bootdg should not contain any disks other than valid root mirror disks. A valid root mirror disk should have mirrors of all volumes in the bootdg. Thus, all disks must be exactly identical in terms of the volumes contained. The given disk access name, daname, or disk media name, dmname, is first checked to see if it is already a valid root disk mirror. If so, the mirror is broken off from the current VxVM root disk, and regenerated into a unique VxVM root disk. If the specified disk is not a valid root disk mirror, and is unused for other purposes, the vxrootmir command is first called to mirror the specified disk from the cur- rent VxVM root disk. After the mirroring operation is complete, the mirror is then broken off, and regenerated into a unique VxVM root disk. OPTIONS
-b Uses the setboot command to set the alternate boot disk to the specified disk. If the -v option is also specified, information is displayed about the current setboot settings. -g diskgroup Specifies the disk group into which the newly broken-off mirror is to be placed. The disk group is created if it does not already exist. If the disk group already exists, the broken-off mirror is added to it. If this option is not specified, the disk group of the broken-off mirror is set to the current default disk group. However, the generation number is made different from the default disk group to prevent the mirror from being automatically imported. -t tasktag Marks any tasks that are registered to track the progress of an operation with the specified tag, tasktag. This option is passed to vxrootmir if it is necessary first to mirror the specified disk that is to be broken off. -v Displays verbose output, including timestamps for operations that are in progress. This option is passed to vxrootmir if it is neces- sary first to mirror the specified disk that is to be broken off. ARGUMENTS
daname Specifies the disk to be used as the broken off mirror by its disk access name (such as c0t2d0). dmname Specifies the disk to be used as the broken off mirror by its disk media name (such as rootdisk03). EXAMPLES
This example shows the vxbrk_rootmir command being executed on a disk that already contains a valid root mirror: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c4t15d0 VxVM vxbrk_rootmir INFO V-5-2-4023 17:47: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4025 17:47: DA c4t15d0s2, DM rootdisk06 is a valid root mirror VxVM vxbrk_rootmir INFO V-5-2-4052 17:47: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 17:47: Breaking off root mirror on DA c4t15d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 17:47: Setting broken off mirror on c4t15d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 17:47: Preparing disk c4t15d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 17:47: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 17:47: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 17:48: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 17:48: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 17:48: Alternate: 0/2/1/0.8.0.255.2.5.0 VxVM vxbrk_rootmir INFO V-5-2-4042 17:48: Making c4t15d0s2 (0/2/1/0.8.0.255.1.15.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 17:48: Disk c4t15d0s2 is now a broken off root disk The next example shows the command being executed on a disk that does not contain a valid root mirror, and which requires vxrootmir be called to mirror the root disk first: /etc/vx/bin/vxbrk_rootmir -g brkdg -vb c5t5d0 VxVM vxbrk_rootmir INFO V-5-2-4023 16:25: Checking specified disk(s) for presence and type VxVM vxbrk_rootmir INFO V-5-2-4043 16:25: Mirroring root disk VxVM vxrootmir INFO V-5-2-2501 16:25: Gathering information on the current VxVM root configuration VxVM vxrootmir INFO V-5-2-2441 16:25: Checking specified disk(s) for usability VxVM vxrootmir INFO V-5-2-2566 16:25: Preparing disk c5t5d0 as a VxVM root disk VxVM vxrootmir INFO V-5-2-3766 16:25: Disk c5t5d0 is now EFI partitioned disk c5t5d0s2 VxVM vxrootmir INFO V-5-2-2410 16:25: Adding disk c5t5d0s2 to brkdg as DM rootdisk03 VxVM vxrootmir INFO V-5-2-1646 16:25: Mirroring all volumes on root disk VxVM vxrootmir INFO V-5-2-1648 16:25: Mirroring volume standvol VxVM vxrootmir INFO V-5-2-1648 16:26: Mirroring volume swapvol VxVM vxrootmir INFO V-5-2-1648 16:30: Mirroring volume rootvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume homevol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume tmpvol VxVM vxrootmir INFO V-5-2-1648 16:31: Mirroring volume usrvol VxVM vxrootmir INFO V-5-2-1648 16:34: Mirroring volume optvol VxVM vxrootmir INFO V-5-2-1648 16:36: Mirroring volume varvol VxVM vxrootmir INFO V-5-2-1616 16:40: Disk c5t5d0s2 is now a mirrored root disk VxVM vxbrk_rootmir INFO V-5-2-4052 16:40: Saving configuration data for later restoration VxVM vxbrk_rootmir INFO V-5-2-4022 16:40: Breaking off root mirror on DA c5t5d0s2 VxVM vxbrk_rootmir INFO V-5-2-4054 16:40: Setting broken off mirror on c5t5d0s2 as unique root disk VxVM vxbrk_rootmir INFO V-5-2-2566 16:40: Preparing disk c5t5d0s2 as a VxVM root disk VxVM vxbrk_rootmir INFO V-5-2-4046 16:41: Patching devnodes, fstab and volboot file in new Root FS VxVM vxbrk_rootmir INFO V-5-2-4045 16:41: Patching /stand/bootconf file to contain new root disk VxVM vxbrk_rootmir INFO V-5-2-2462 16:41: Current setboot values: VxVM vxbrk_rootmir INFO V-5-2-4048 16:41: Primary: 0/0/2/0.2.0 VxVM vxbrk_rootmir INFO V-5-2-4010 16:41: Alternate: 0/2/1/0.8.0.255.2.0.0 VxVM vxbrk_rootmir INFO V-5-2-4042 16:41: Making c5t5d0s2 (0/2/1/0.8.0.255.2.5.0) the alternate boot disk VxVM vxbrk_rootmir INFO V-5-2-4028 16:41: Disk c5t5d0s2 is now a broken off root disk SEE ALSO
vxbootsetup(1M), vxdg(1M), vxintro(1M), vxrootmir(1M), vxtask(1M) VxVM 5.0.31.1 24 Mar 2008 vxbrk_rootmir(1M)
All times are GMT -4. The time now is 01:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy