LDOMS IO Best Practices - Network Availability With Logical Domains


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris BigAdmin RSS LDOMS IO Best Practices - Network Availability With Logical Domains
# 1  
Old 09-30-2008
LDOMS IO Best Practices - Network Availability With Logical Domains

This Sun BluePrints Series article maps I/O best practices from the physical world to the virtual world supported by Logical Domains, for example, by explaining how to use multiple network connections to a server when the connections--and the server itself--are virtual.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Solaris

Logical Domains Manager

Hi, I just did install Solaris 11 in Sun Fire T2000. From research i did, latest LDM does not support on T2000. So where i can download the version that supported in T2000 machine? I don't have access to oracle edelivery. Please assist me. Thanks. (0 Replies)
Discussion started by: mzainal
0 Replies

2. Solaris

Booting Solaris LDOMS Control Domains

We are having a discussion on what order LDOMS and control domains should be booted. I think it should be LDOMS first then Control. Can anyone tell me why I am wrong or why I am right. Thanks, :confused: (6 Replies)
Discussion started by: aeroforce
6 Replies

3. Solaris

Migrating Solaris 8, 9 to Guest Domains (LDOMs)

Hi Everyone, one question is it possible to migrate a physical standalone Solaris 8 or 9 OS to Guest Domain (LDOMs). If yes, can someone please provide steps to migrate these OS to LDOMs. Thanks, Kartheek. (1 Reply)
Discussion started by: bobby320
1 Replies

4. Solaris

Minimum Testsystem for Logical Domains

Hi, i'm relative new to solaris 10 and my new boss want to go for Logical Domains in our server-environment. I would like to get used to it using a little sun-Machine at my Home. What do i need to try logical Domains? As i read here http://www.sun.com/blueprints/0207/820-0832.pdf i... (1 Reply)
Discussion started by: Pilot Pirx
1 Replies
Login or Register to Ask a Question
LVDISPLAY(8)						      System Manager's Manual						      LVDISPLAY(8)

NAME
lvdisplay - display attributes of a logical volume SYNOPSIS
lvdisplay [-a|--all] [-c|--colon] [-d|--debug] [-h|-?|--help] [--ignorelockingfailure] [--ignoreskippedcluster] [--maps] [--nosuffix] [-P|--partial] [--units hHbBsSkKmMgGtTpPeE] [-v|--verbose] [--version] [LogicalVolumePath [LogicalVolumePath...]] lvdisplay --columns|-C [--aligned] [-a|--all] [-d|--debug] [-h|-?|--help] [--ignorelockingfailure] [--ignoreskippedcluster] [--noheadings] [--nosuffix] [-o|--options [+]Field[,Field...]] [-O|--sort [+|-]Key1[,[+|-]Key2...]] [-P|--partial] [--segments] [--separator Separator] [--unbuffered] [--units hHbBsSkKmMgGtTpPeE] [-v|--verbose] [--version] [LogicalVolumePath [LogicalVolumePath...]] DESCRIPTION
lvdisplay allows you to see the attributes of a logical volume like size, read/write status, snapshot information etc. lvs(8) is an alternative that provides the same information in the style of ps(1). lvs(8) is recommended over lvdisplay. OPTIONS
See lvm(8) for common options and lvs for options given with --columns. --all Include information in the output about internal Logical Volumes that are components of normally-accessible Logical Volumes, such as mirrors, but which are not independently accessible (e.g. not mountable). For example, after creating a mirror using lvcreate -m1 --mirrorlog disk, this option will reveal three internal Logical Volumes, with suffixes mimage_0, mimage_1, and mlog. -c, --colon Generate colon separated output for easier parsing in scripts or programs. N.B. lvs(8) provides considerably more control over the output. The values are: * logical volume name * volume group name * logical volume access * logical volume status * internal logical volume number * open count of logical volume * logical volume size in sectors * current logical extents associated to logical volume * allocated logical extents of logical volume * allocation policy of logical volume * read ahead sectors of logical volume * major device number of logical volume * minor device number of logical volume -m, --maps Display the mapping of logical extents to physical volumes and physical extents. To map physical extents to logical extents use: pvs --segments -o+lv_name,seg_start_pe,segtype --columns, -C Display output in columns, the equivalent of lvs. Options listed are the same as options given in lvs(8). Examples Shows attributes of that logical volume. If snapshot logical volumes have been created for this original logical volume, this command shows a list of all snapshot logical volumes and their status (active or inactive) as well: lvdisplay -v /dev/vg00/lvol2 Shows the attributes of this snapshot logical volume and also which original logical volume it is associated with: lvdisplay /dev/vg00/snapshot SEE ALSO
lvm(8), lvcreate(8), lvs(8), lvscan(8), pvs(8) Sistina Software UK LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26) LVDISPLAY(8)