Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Solaris Volume Manager Striping Considerations

Software striping is becoming far less necessary as more intelligent hardware storage solutions emerge. Before considering Solaris Volume Manager striping, investigate the capabilities of your current I/O subsystem. If software striping is still deemed necessary, then take care when configuring the volumes.

The main problem with Solaris Volume Manager striping is split I/O. Splitting of an individual I/O operation to more than one disk degrades performance. There are several ways to avoid this:

  • Use hardware striping where possible. This prevents Solaris Volume Manager software or the operating system from having to split an I/O operation.

  • Increase the stripe width to lessen the frequency of splitting an I/O operation.

  • Calculate alignment based on the I/O size and offsets. This works well for databases with a known I/O size.

Increase the Default Solaris Volume Manager Stripe Width

The probability of splitting an I/O operation is inversely proportional to the stripe width. Consider an OLTP system which mostly performs 8-Kbyte I/O. A 32-Kbyte stripe width has a probability of splitting 1 of 4 I/O operations, whereas a 1-Mbyte stripe width splits only 1 of 128 I/O operations (less than one percent). Increasing the stripe width is the single most important improvement you can make to decrease the probability of splitting an I/O operation.

Make the Stripe Width Large Relative to the I/O Size

If you use the metainit command without the -i option, Solaris Volume Manager software uses a default of 16 Kbytes for the stripe width. A narrow stripe width doesn't allow the application to take advantage of read-ahead for sequential I/O provided by the underlying storage subsystem. A stripe width of 1 Mbyte or greater is common, especially when implementing a stripe and mirror everywhere (SAME) strategy.

Align Soft Partitions on the Stripe Boundary

Before the Solaris 8 OE Solaris Volume Manager software, each volume had to match a hard disk partition or volume table of contents (VTOC). With this older scheme, there is a direct relationship between a Solaris Volume Manager device and the physical disk or LUN. This scheme limits the number of volumes to the number partitions or VTOCs that can be created.

Soft partitioning enables one piece of disk to be partitioned into more slices than is possible by a device VTOC. Soft partitioning provides a great amount of flexibility because it enables volumes to be created on top of individual disks or existing Solaris Volume Manager volumes. Layering of volumes is particularly useful with large RAID devices, which can easily exceed 1 terabyte. But soft partitioning on top of striped hard partitions can lead to the split I/O problem.

As mentioned, if the stripe width is large compared to the I/O size, there is less splitting of I/O. In the case where 8 Kbytes is the I/O size and 1 Mbyte is the stripe width, less than one percent of the I/O operations are split. But still, there are some split I/O operations. To get total alignment, striped soft partitions must be aligned on a stripe boundary.

Consider the example of an Oracle application that uses an 8-Kbyte block size. The following example shows the default soft partitions or layered volumes that are created with the metainit command.

# metainit d10 1 2 c3t1d0s7 c5t1d0s7 -i 256k
# metainit d11 -p d10 1024m
# metainit d12 -p d10 1024m

Meta device d11 happens to begin on a stripe boundary as shown in FIGURE 2. Random block reads to this device are exactly 8 Kbytes in size and involve exactly one disk. Due to the 512-byte label added to a soft partition, meta device d12 will split I/O that falls on the stripe boundary.

Figure 2FIGURE 2 Split I/O Due to Watermark

To correct this, use the -o option to specify the offset to be a multiple of the stripe width. The following example shows how to use the -o option with the metainit command to specify the starting offset of the soft-partition to align on the stripe boundary.

# metainit d10 1 2 c3t1d0s7 c5t1d0s7 -i 256k
# metainit d11 -p d10 -o 512 -b 2097152

Taking this example one step further, use the following formula to determine the next offset:

nextoffset = last_offset + last_size + stripe_width (in 512-byte blocks)

For this example, the result is:

512 + 2097152 + 512 = 2098176 blocks

The corresponding metainit command:

# metainit d12 -p d10 -o 2098176 -b 2097152

This offset guarantees that the d12 meta device starts on a stripe boundary and that the 8-Kbyte I/O will not be split unnecessarily.

To administer volumes using this scheme, you must keep track of offsets. While this is easy during the initial creation of volumes, it is useful to be able to observe the current settings. The following example shows how the metastat -p command can be used to show the volume offsets. This command is useful for documenting the storage configuration as well as for ongoing administration.

# metastat -p |egrep 'd2' 
 d208 -p d2 -o 61473953 -b 9680 
 d2 1 1 c5t1d0s0
 d207 -p d2 -o 61464272 -b 9680 
 d206 -p d2 -o 60440255 -b 1024016 
 d205 -p d2 -o 59416238 -b 1024016 
 d204 -p d2 -o 52264621 -b 7151616 
 d203 -p d2 -o 45113004 -b 7151616 
 d202 -p d2 -o 37961387 -b 7151616 
 d201 -p d2 -o 30809770 -b 7151616 
 d29 -p d2 -o 25677481 -b 5132288 
 d28 -p d2 -o 20545192 -b 5132288 
 d27 -p d2 -o 15412903 -b 5132288 
 d26 -p d2 -o 10280614 -b 5132288 
 d25 -p d2 -o 5148325 -b 5132288 
 d24 -p d2 -o 16036 -b 5132288 
 d23 -p d2 -o 10691 -b 5344 
 d22 -p d2 -o 5346 -b 5344 
 d21 -p d2 -o 1 -b 5344 

Make the Software Stripe Width a Multiple of the Hardware Segment Size

Hardware RAID and software RAID are sometimes combined to increase availability and throughput, but there can be performance consequences if the underlying storage layout is not considered.

Make sure that you understand the stripe unit or segment size of the underlying storage architecture when implementing software striping on top of hardware RAID. Failure to do this can cause a single I/O operation to be split between multiple devices on the underlying storage. This unwanted split I/O operation increases latency and degrades overall throughput.

The underlying segment size differs from array to array. For example:

  • Sun StorEdge 9980 system uses a 48-Kbyte segment size.

  • Sun StorEdge 6910 system and Sun StorEdge T3 arrays use 32-Kbyte or 64-Kbyte segment size (64-Kbyte provides the best performance).

When combining multiple LUNs, it is best to use a fairly large stripe width. For the StorEdge 9980 example, a stripe width of 20 * 48 Kbytes, or 960 Kbytes, is a good place to start for an expected 8-Kbyte I/O size. This enables the LUN to benefit from read-ahead while reducing the probability of splitting an I/O operation.

Limit Striping and Meta Devices

When coming from a Veritas background, there is a tendency to want to map Veritas concepts to Solaris Volume Manager software. VxVM creates subdisks for every portion of disk that is used in a stripe. This can be simulated with Solaris Volume Manager software by using soft-partitions. There are no performance implications, but this technique can use an excessively large number of meta devices, especially as the number of devices in a stripe is increased.

Consider an example where 200 volumes are created as stripes across 16 drives. If a soft-partition is created for each subdisk, a total of 16*200+200 = 3400 meta devices is needed. If the soft-partitions are created on top of a striped hard partition, only 1+200 = 201 meta devices are needed.

By default, Solaris Volume Manager software can create only 128 meta devices. You can increase this to a maximum of 8192 by modifying the nmd field in the /kernel/drv/md.conf file. To get this to take effect, the machine must be rebooted with boot -r. This procedure is discussed in more detail in the Solaris Volume Manager software administration guide.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020