Sponsored Content
Full Discussion: Cannot extend logical volume
Operating Systems AIX Cannot extend logical volume Post 302986498 by Scrutinizer on Saturday 26th of November 2016 03:09:17 AM
Old 11-26-2016
Indeed as a rule the combination of lvm striping with high end SAN storage (double or triple striping) is to be avoided, both for reasons of simplicity and performance.

Remarkably perhaps, I have come across situations, where lvm striping actually did make a serious performance difference (improvement) with high end SAN Storage and sequential read IO, but only with a narrow width (say 4-8) at small stripe sizes (128KiB-256KiB).

This was because there was a front-end bottle neck and at the same it was difficult to increase IO queue sizes, which is extra important because of the serial nature of Fibre Channel SANs (the bottle neck could even be observed when the cache-hit ratio was at 100% at the front-end storage level).

By using narrow striping it was possible to increase the effective IO queue size, while at the same time not confusing the prefetch algorithms of the SAN storage. The LUN's in the LVM narrow stripe had to be from different physical disk sets in the backend SAN Storage level, in case of a storage array architecture where this would make a difference). At the SAN storage, this translated in a nice even spread of backend usage, without hot spots.

Situations where this mattered was with databases with quite a bit of sequential read IO. This happened with Oracle databases that were never fully optimized, because the standard query specifications kept changing, which in my experience is the situation that occurs often. Another situation is when out of necessity reports or other batches need to run during on-line usage.

Conversely, I have come across a situation where a large stripe size was used (4 MiB) with a large stripe width (16) and that really confused storage, thwarting the prefetch algorithms, and all IO was done with small sizes, bringing sequential read IO to a crawl, while the storage processors were working overtime.

So as usual in performance tuning: "it depends...." Smilie

Last edited by Scrutinizer; 11-26-2016 at 08:19 AM..
 

10 More Discussions You Might Find Interesting

1. AIX

Extend one Logical Volume

Hi All, I am new to AIX. I need to extend one Logical Volume it is jfs type on On AIX 5.1. I have enough free space on the volume group for this extension Can I use smitty chjfs , will this do it without interruptions to the application that is using this Logical Volume. Thanks Scampi (1 Reply)
Discussion started by: scampi
1 Replies

2. UNIX for Advanced & Expert Users

LVM - Extending Logical Volume within Volume Group

Hello, I have logical volume group of 50GB, in which I have 2 logical volumes, LogVol01 and LogVol02, both are of 10GB. If I extend LogVol01 further by 10GB, then it keeps the extended copy after logical volume 2. I want to know where it keeps this information Regards Himanshu (3 Replies)
Discussion started by: ghimanshu
3 Replies

3. AIX

Help - can't extend logical volume ?

Hi, Smit "Increase the Size of a Logical Volume" command failed. Output: ---------------------------------------------------------- Command: failed stdout: yes stderr: no Before command completion, additional instructions may appear below. The distribution of this command (111) failed on... (2 Replies)
Discussion started by: vilius
2 Replies

4. 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

5. AIX

Logical volume name conflict in two volume group

Hello, I am a french computer technician, and i speak English just a little. On Aix 5.3, I encounter a name conflict logical volume on two volume group. The first volume lvnode01 is OK in rootvg and mounted. It is also consistent in the ODM root # lsvg -l rootvg |grep lvnode01 ... (10 Replies)
Discussion started by: dantares
10 Replies

6. HP-UX

Unable To Extend the Size of a Logical Volume File System

Background: # uname -a HP-UX deedee B.11.23 U ia64 4294967295 unlimited-user license deedee.rsn.hp.com:/ # bdf /opt Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol6 6553600 6394216 158144 98% /opt /opt is almost full... (3 Replies)
Discussion started by: Rob Sandifer
3 Replies

7. 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

8. HP-UX

[Solved] How to extend a mirrored logical volume?

Want to extend the /home filesystem: Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol4 262144 260088 2056 99% /home root@server:./root # vgdisplay vg00 --- Volume groups --- VG Name /dev/vg00 VG Write Access read/write VG Status available Max LV 255 Cur LV 11 Open... (4 Replies)
Discussion started by: proactiveaditya
4 Replies

9. AIX

Position of the logical volume on the physical volume

Hello everyone, I just read that while creating a logical volume(LV) we can choose the region of the physical volume (PV) in which the LV should be created. When I say region I mean: outer edge - outer middle - center - inner middle and inner edge. Can anyone help me understand the utility... (11 Replies)
Discussion started by: adilyos
11 Replies

10. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies
DBIx::Class::Storage::DBI::Replicated::Balancer(3pm)	User Contributed Perl Documentation   DBIx::Class::Storage::DBI::Replicated::Balancer(3pm)

NAME
DBIx::Class::Storage::DBI::Replicated::Balancer - A Software Load Balancer SYNOPSIS
This role is used internally by DBIx::Class::Storage::DBI::Replicated. DESCRIPTION
Given a pool (DBIx::Class::Storage::DBI::Replicated::Pool) of replicated database's (DBIx::Class::Storage::DBI::Replicated::Replicant), defines a method by which query load can be spread out across each replicant in the pool. ATTRIBUTES
This class defines the following attributes. auto_validate_every ($seconds) If auto_validate has some sort of value, run "validate_replicants" in DBIx::Class::Storage::DBI::Replicated::Pool every $seconds. Be careful with this, because if you set it to 0 you will end up validating every query. master The DBIx::Class::Storage::DBI object that is the master database all the replicants are trying to follow. The balancer needs to know it since it's the ultimate fallback. pool The DBIx::Class::Storage::DBI::Replicated::Pool object that we are trying to balance. current_replicant Replicant storages (slaves) handle all read only traffic. The assumption is that your database will become readbound well before it becomes write bound and that being able to spread your read only traffic around to multiple databases is going to help you to scale traffic. This attribute returns the next slave to handle a read request. Your "pool" attribute has methods to help you shuffle through all the available replicants via its balancer object. METHODS
This class defines the following methods. _build_current_replicant Lazy builder for the "current_replicant_storage" attribute. next_storage This method should be defined in the class which consumes this role. Given a pool object, return the next replicant that will serve queries. The default behavior is to grab the first replicant it finds but you can write your own subclasses of DBIx::Class::Storage::DBI::Replicated::Balancer to support other balance systems. This returns from the pool of active replicants. If there are no active replicants, then you should have it return the master as an ultimate fallback. around: next_storage Advice on next storage to add the autovalidation. We have this broken out so that it's easier to break out the auto validation into a role. This also returns the master in the case that none of the replicants are active or just just forgot to create them :) increment_storage Rolls the Storage to whatever is next in the queue, as defined by the Balancer. around: select Advice on the select attribute. Each time we use a replicant we need to change it via the storage pool algorithm. That way we are spreading the load evenly (hopefully) across existing capacity. around: select_single Advice on the select_single attribute. Each time we use a replicant we need to change it via the storage pool algorithm. That way we are spreading the load evenly (hopefully) across existing capacity. before: columns_info_for Advice on the current_replicant_storage attribute. Each time we use a replicant we need to change it via the storage pool algorithm. That way we are spreading the load evenly (hopefully) across existing capacity. _get_forced_pool ($name) Given an identifier, find the most correct storage object to handle the query. AUTHOR
John Napiorkowski <jjnapiork@cpan.org> LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.14.2 2011-01-31 DBIx::Class::Storage::DBI::Replicated::Balancer(3pm)
All times are GMT -4. The time now is 01:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy