02-27-2019
Can you change the hdisk max_transfer size from 0x80000 to 0x40000 and re-test? You will have to unmount the filesystem, varyoff the VG and run the chdev command.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
can someone tell me a good site to go to in order to learn this. please do not recommen nay books because i dont have interest in that. if you know of any good sites with good straight forward explanation on how to split loads on machines that has excessive loading, please let me know
Also,... (1 Reply)
Discussion started by: TRUEST
1 Replies
2. Filesystems, Disks and Memory
Hi all,
long time ago I posted something, but now, it is needed again :(
Currently, I am handling with a big NFS Server for more than 200 clients, this sever has to work with 256 NFSDs. Because of this huge amount of NFSDs, there are thousands of small write accesses down to the disk and... (3 Replies)
Discussion started by: malcom
3 Replies
3. UNIX for Dummies Questions & Answers
Hi to all,
I'm interested in finding an introduction about Performance Tuning under Unix (or Linux); can somebody please point me in the right direction?
Best regards (1 Reply)
Discussion started by: domyalex
1 Replies
4. Shell Programming and Scripting
Sorry,
This is out of scope of this group.But I require the clarification pretty urgently.
My Oracle database is parallely enabled.
Still,in a particular table queries do not work "parallely" always.
How is this? (9 Replies)
Discussion started by: kthri
9 Replies
5. Shell Programming and Scripting
Hi All,
In last one week, i have posted many questions in this portal. At last i am succeeded to make my 1st unix script.
following are 2 points where my script is taking tooooo long.
1. Print the total number of records excluding header & footer. I have found that awk 'END{print NR -... (2 Replies)
Discussion started by: Amit.Sagpariya
2 Replies
6. AIX
How to do Performance monitoring and tuning in AIX. (2 Replies)
Discussion started by: AIXlearner
2 Replies
7. AIX
Hi all,
From Googling, I found that the basics used for troubleshooting UNIX/AIX performance issues are commands like vmstat, iostat and sar. I believe these are generic commands regardless of what UNIX flavour is in used, only difference being is the format of the output.
In a real case... (2 Replies)
Discussion started by: newbie_01
2 Replies
8. AIX
Please take a look at this system and give your analysis / advice. Can it be tuned to get a better performance?
We are not getting more hardware ressources at the moment.
We have to live with what we have. Application running on the system is SAS. OS is AIX 6.1
Let me know if you need output of... (7 Replies)
Discussion started by: firefox111
7 Replies
9. Solaris
Dear all,
I have a Local zone , where users feel that performance is not good.
Is it wise to collect the inputs from the local zone rather than taking from the global zone.
And also Can I tune from Global zone , so that it will reflect in local zone.
Rgds
rj (2 Replies)
Discussion started by: jegaraman
2 Replies
10. Tips and Tutorials
Overview:
Introduction
What Does Success Mean?
What Does Performance Mean?
Every Picture is Worth a Thousand Words
Work Like a Physicist
Work Like You Walk - One Step at a Time
Learn to Know Your System
Choose Your Weapons!
Tools of the Trade 1 - vmstat
A Little Theory Along the Way -... (1 Reply)
Discussion started by: bakunin
1 Replies
LEARN ABOUT DEBIAN
gfs2_jadd
gfs2_jadd(8) System Manager's Manual gfs2_jadd(8)
NAME
gfs2_jadd - Add journals to a GFS2 filesystem
SYNOPSIS
gfs2_jadd [OPTION]... <DEVICE|MOINTPOINT>...
DESCRIPTION
gfs2_jadd is used to add journals (and a few other per-node files) to a GFS2 filesystem. When this operation is complete, the journal
index is updated so that machines mounting the filesystem at a later date will see the newly created journals in addition to the journals
already there. Machines which are already running in the cluster are unaffected.
You may only run gfs2_jadd on a mounted filesystem, addition of journals to unmounted filesystems is not supported. You only need to run
gfs2_jadd on one node in the cluster. All the other nodes will see the expansion has occurred when required.
You must be superuser to execute gfs2_jadd. The gfs2_jadd tool tries to prevent you from corrupting your filesystem by checking as many of
the likely problems as it can. When growing a filesystem, only the last step of updating the journal index affects the currently mounted
filesystem and so failure part way through the expansion process should leave your filesystem in its original state.
OPTIONS
-c MegaBytes
Initial size of each journal's quota change file
-D Print out debugging information about the filesystem layout.
-h Prints out a short usage message and exits.
-J size
The size of the new journals in megabytes. The defaults to 32MB (the minimum size allowed is 8MB). If you want to add journals of
different sizes to the filesystem, you'll need to run gfs2_jadd once for each different size of journal.
-j num The number of new journals to add.
-q Be quiet. Don't print anything.
-u MegaBytes
Initial size of each journal's unlinked tag file
-V Version. Print version information, then exit.
SEE ALSO
mkfs.gfs2(8) gfs2_grow(8)
gfs2_jadd(8)