08-25-2009
You may also want to set, depending on your RAM, a read ahead of say 4MB or more as well as a stride in the file system that matches your work pattern.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
I am working on MSR110 ...Can anyone plz tell me how to use the configuration commands with magnetic reader???. Please help me out as i have to develop API in C on linux platform.MSR110 is not responding to the configuration commands.
Please help...
Regards
Mahima (0 Replies)
Discussion started by: mahima_er
0 Replies
2. UNIX for Advanced & Expert Users
Hi,
Is there are any special preocedure for extending veritas mirror-stripe volume? In my case , volume lay out looks as below
v test - ENABLED ACTIVE 419430400 SELECT - fsgen
pl test-01 test ENABLED ACTIVE 419454720 STRIPE 3/128 RW
sd... (0 Replies)
Discussion started by: 2k7.vipin
0 Replies
3. AIX
Hello all.
I have a volume group with 8 PV's, and a logical volume striped across these 8 volumes.
However, an lslv is showing:
STRIPE WIDTH: 9
STRIPE SIZE: 64k
There's really only eight disks, so how can the stripe width be 9?
ODM also showed this:
# odmget CuAt |... (4 Replies)
Discussion started by: Scott
4 Replies
4. Emergency UNIX and Linux Support
Hi all
I have just had SAN allocate 4*30 GB of disks and had created a new scalable vg and assigned the disks to it:
I used smitty to create vg and the command is: x -y'vgdata1' hdisk82 hdisk83 hdisk84 hdisk85
root@aadcxs08 / : lsvg vgdata1
VOLUME GROUP: vgdata1 VG... (4 Replies)
Discussion started by: hedkandi
4 Replies
5. AIX
Hello,
I have a scsi pci x raid controller card on which I had created a disk array of 3 disks
when I type lspv ; I used to see 3 physical disks ( two local disks and one raid 5 disk )
suddenly the raid 5 disk array disappeared ; so the hardware engineer thought the problem was with SCSI... (0 Replies)
Discussion started by: filosophizer
0 Replies
6. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
7. Solaris
Hello Admins..
I am going through solaris volume manager guide for RAID-0 concatenation and stripes, I do not understand the concept of stripe from following example of concatenation.
There is an eample for concatenation:
# metainit d25 1 1 c0t1d0s2
d25: Concat/Stripe is setup
the... (5 Replies)
Discussion started by: snchaudhari2
5 Replies
8. Red Hat
Hello,
I want to delete a RAID configuration an old server has.
Since i haven't the chance to work with the specific raid controller in the past can you please help me how to perform the configuraiton?
I downloaded IBM ServeRAID Support CD but i wasn't able to configure the video card so i... (0 Replies)
Discussion started by: @dagio
0 Replies
9. Shell Programming and Scripting
Say i have:
g_gateway domain="abc.com" to="123.123.123.123" relay="false"
how do i use awk or sed or any method to get the result below:
abc.com 123.123.123.123 (3 Replies)
Discussion started by: timmywong
3 Replies
LEARN ABOUT CENTOS
sd_readahead
SD_READAHEAD(3) sd_readahead SD_READAHEAD(3)
NAME
sd_readahead - Control ongoing disk boot-time read-ahead operations
SYNOPSIS
#include "sd-readahead.h"
int sd_readahead(const char *action);
DESCRIPTION
sd_readahead() may be called by programs involved with early boot-up to control ongoing boot-time disk read-ahead operations. It may be
used to terminate read-ahead operations in case an uncommon disk access pattern is to be expected and hence read-ahead replay or collection
is unlikely to have the desired speed-up effect on the current or future boot-ups.
The action should be one of the following strings:
cancel
Terminates read-ahead data collection, and drops all read-ahead data collected during this boot-up.
done
Terminates read-ahead data collection, but keeps all read-ahead data collected during this boot-up around for use during subsequent
boot-ups.
noreplay
Terminates read-ahead replay.
RETURN VALUE
On failure, these calls return a negative errno-style error code. It is generally recommended to ignore the return value of this call.
NOTES
This function is provided by the reference implementation of APIs for controlling boot-time read-ahead and distributed with the systemd
package. The algorithm it implements is simple, and can easily be reimplemented in daemons if it is important to support this interface
without using the reference implementation.
Internally, this function creates a file in /run/systemd/readahead/ which is then used as flag file to notify the read-ahead subsystem.
For details about the algorithm check the liberally licensed reference implementation sources:
http://cgit.freedesktop.org/systemd/systemd/plain/src/readahead/sd-readahead.c and
http://cgit.freedesktop.org/systemd/systemd/plain/src/systemd/sd-readahead.h
sd_readahead() is implemented in the reference implementation's drop-in sd-readahead.c and sd-readahead.h files. It is recommended that
applications consuming this API copy the implementation into their source tree. For more details about the reference implementation, see
sd-readahead(3)
If -DDISABLE_SYSTEMD is set during compilation, this function will always return 0 and otherwise become a NOP.
EXAMPLES
Example 1. Cancelling all read-ahead operations
During boots where SELinux has to relabel the file system hierarchy, it will create a large amount of disk accesses that are not necessary
during normal boots. Hence it is a good idea to disable both read-ahead replay and read-ahead collection.
sd_readahead("cancel");
sd_readahead("noreplay");
SEE ALSO
systemd(1), sd-readahead(3), daemon(7)
systemd 208 SD_READAHEAD(3)