02-02-2011
Hi there.. it's actually 11.23, which is new to me to be honest
I tried adding a bit more swap on disk to see if the o/s would release some RAM, but it didn't, not a bit. I also found that the SFM processes (EMS) was holding over 25GB RAM, so I stopped that, but that made no difference.. grabbing at straws really. I've now built another system, exactly the same spec and run up the same amount of VM's and it still has 54GB of free RAM, so it looks like a hardware fault with RAM.
Thanks for replying to my thread
10 More Discussions You Might Find Interesting
1. SCO
After rebuilding the RAIDs on the SCO Unix, the following dialog appears when rebooting the machine.
Fssat: /dev/boot mounted
Mounted /stand filesystem
Fsstat: /dev/usr1 okay
Mounted /usr1 filesystem
(continues usr2, usr3,
Fsstat: /dev/usr4 okay
Panic: HTFS: Bad directory ino... (2 Replies)
Discussion started by: Mac Tire
2 Replies
2. AIX
Hi,
I'm trying to create a new group on an AIX 5.2.0.0. server but am getting the following error:
root:/root $ mkgroup debt
3004-698 Error committing changes to "debt" : Value is invalid.
I've change the group name to no affect.
Does anyone have any ideas what could be causing this?
... (0 Replies)
Discussion started by: m223464
0 Replies
3. Solaris
Hello friend,
Now i'm doing JDS3.1 in v440 servers.while checking the lustatus command
getiing out like this
lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
-------------------------- --------... (0 Replies)
Discussion started by: rjay.com
0 Replies
4. Red Hat
Hi,
On server 64bit Hw Arch , Linux 5.0(32bit) is installed it is showing only 3gb of ram though physical is 16gb
can u give me idea why? (4 Replies)
Discussion started by: manoj.solaris
4 Replies
5. Red Hat
Hi, I am having similar issue showing filesystem 100% even after deleting the files. I understood the issue after going through this chain. But i can not restart the processes being oracle database. Is there way like mounting filesytem with specific options would avoid happening this issue.
How... (0 Replies)
Discussion started by: prashant185
0 Replies
6. Red Hat
I have directory that has some billion file inside , i tried copy some files for specific date but it's always did not respond for long time and did not give any result.. i tried everything with find command and also with xargs..
even this command find . -mtime -2 -print | xargs ls -d did not... (2 Replies)
Discussion started by: before4
2 Replies
7. HP-UX
Hi,
I am trying to tar a directory structure. but unable to do due to a symbolic link. Please help
indomt@behpux $ tar -cvf test.tar /home/indomt
a /home/indomt symbolic link to /dxdv/03/ap1dm1
Thanks (1 Reply)
Discussion started by: nag_sathi
1 Replies
8. HP-UX
Hi All ,
Here we have 1 physical machine followed by 5 guest machine under HPVM.
Version HPVM -- B.04.20 -- Integrity VM HPVM
The main role of the base machine is to serve all the guest machine .
What is the best procedure to restart all the host and guest ... (0 Replies)
Discussion started by: marunmeera
0 Replies
9. AIX
Hi everyone!
Ok so I'm trying for the first time to install AIX on a LPAR with NIM.
The NIM:
root@oaexpnimp01(/home/root) # oslevel -s
6100-08-02-1316
I'm trying to install AIX 6.1 TL1. I successfully created a new lpp source
root@oaexpnimp01(/home/root) # lsnim -l AIX61_TL1_2... (10 Replies)
Discussion started by: trivium012
10 Replies
10. Forum Support Area for Unregistered Users & Account Problems
Hi.
I registered, but when trying to post, I get ...
"Sorry, you do not have enough Bits to post a new thread"
Google & Forum search showed some hits, but no solution.
Please advide.
Thanks! (1 Reply)
Discussion started by: gehe
1 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)