08-25-2009
Quote:
Originally Posted by
mark54g
You can set the amount of caching being done whenever a read is going on, but that will use more RAM.
the perc 5 it self has 512mb of ram.. u have any link giving more info about this?
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
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)