10-02-2003
Issue the command "cat /proc/meminfo" for the memory info. Now this is just a guess!! If you issue the command "cat /proc/mtrr" the output will be something like this with one RAM stick installed;
"reg00: base=0x00000000 ( 0MB), size= 64MB: write-back, count=1"
and the output of "cat /proc/mtrr" on a system with two RAM cards;
"reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1
reg01: base=0xf5000000 (3920MB), size= 8MB: write-combining, count=1"
I was in similar scenario recently where I had to assess a machine for upgrade. One of the parameters required was how many of the RAM slots were populated, I used the above method, when I brought the server down for the upgrade, two slots populated. Alocate a time window when the server is not too busy, 3am if necassary, bring it offline and have a look inside.
Throw the Dell into the sea and buy a Sun machine running Solaris! Dell make great desktops, crap servers!!
Oh yeah, another way would be to get the shipping details from Dell.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Does anyone know the command to configure HP tape slots. I have tried the following on Sun, but its notworking. This is the first time I have configured a tape drive with muiltple slots.
root@ssdb0009 # cfgadm -l
Ap_Id Type Receptacle Occupant Conditio... (3 Replies)
Discussion started by: dennisca
3 Replies
2. Solaris
I am setting up a Storedge Multipack and upon booting(stop + a) I did a probe-scsi all.
Is there any way of viewing this output one page at a time?....it scrolls by too fast and I cannot get all the info.
Also it lists the drives here, but after logging in format does not show them.
How... (7 Replies)
Discussion started by: finster
7 Replies
3. Solaris
Hi folks,
I´m having a problem with a Ultra60 box with diff scsi pci card
conected to one D1000. The conection are correct because a checked the
D1000 guide. When a do probe-scsi-all in the OBP, the D1000 blink all
disks one time then the led of one of the disks powers off and then
nothing... (2 Replies)
Discussion started by: spacewalker
2 Replies
4. Solaris
I'm looking for open PCI slots in our array of sun boxes. I need help on how to distinguish if there's an open slot or not using prtdiag and prtconf. Is there a better tool for this? TIA.
Here's my prtdiag -v | grep pci:
pci 66 PCI5 SUNW,qlc-pci1077,2312 (scsi-+
... (9 Replies)
Discussion started by: revzalot
9 Replies
5. Solaris
Hi All,
Can Any body tell me how to find out the how many memory slots are there in SUN server ??
Thanks and Regards, (2 Replies)
Discussion started by: lbreddy
2 Replies
6. AIX
Hi, all. I was wondering if there's a command or log file that will tell me how much RAM is in the system and, more specifically, the size of each stick.
Thanks,
Jason (3 Replies)
Discussion started by: JasonRkr
3 Replies
7. Solaris
How do I find any available PCI slots on a v440?
When I run prtconf, I get the following output? But I am not able to make out whether all the PCI slots are used.
================================= IO Devices =================================
Bus Freq
Brd Type MHz Slot ... (1 Reply)
Discussion started by: jtamminen
1 Replies
LEARN ABOUT CENTOS
tapset::nfs_proc
tapset::nfs_proc(3stap) tapset::nfs_proc(3stap)
NAME
tapset::nfs_proc - systemtap nfs_proc tapset
DESCRIPTION
nfs.proc.lookup
NFS client opens/searches a file on server
See probe::nfs.proc.lookup(3stap)
for details.
nfs.proc.read
NFS client synchronously reads file from server
See probe::nfs.proc.read(3stap)
for details.
nfs.proc.write
NFS client synchronously writes file to server
See probe::nfs.proc.write(3stap)
for details.
nfs.proc.commit
NFS client committing data on server
See probe::nfs.proc.commit(3stap)
for details.
nfs.proc.read_setup
NFS client setting up a read RPC task
See probe::nfs.proc.read_setup(3stap)
for details.
nfs.proc.read_done
NFS client response to a read RPC task
See probe::nfs.proc.read_done(3stap)
for details.
nfs.proc.write_setup
NFS client setting up a write RPC task
See probe::nfs.proc.write_setup(3stap)
for details.
nfs.proc.write_done
NFS client response to a write RPC task
See probe::nfs.proc.write_done(3stap)
for details.
nfs.proc.commit_setup
NFS client setting up a commit RPC task
See probe::nfs.proc.commit_setup(3stap)
for details.
nfs.proc.commit_done
NFS client response to a commit RPC task
See probe::nfs.proc.commit_done(3stap)
for details.
nfs.proc.open
NFS client allocates file read/write context information
See probe::nfs.proc.open(3stap)
for details.
nfs.proc.release
NFS client releases file read/write context information
See probe::nfs.proc.release(3stap)
for details.
nfs.proc.handle_exception
NFS client handling an NFSv4 exception
See probe::nfs.proc.handle_exception(3stap)
for details.
nfs.proc.create
NFS client creating file on server
See probe::nfs.proc.create(3stap)
for details.
nfs.proc.remove
NFS client removes a file on server
See probe::nfs.proc.remove(3stap)
for details.
nfs.proc.rename
NFS client renames a file on server
See probe::nfs.proc.rename(3stap)
for details.
SEE ALSO
probe::nfs.proc.lookup(3stap), probe::nfs.proc.read(3stap), probe::nfs.proc.write(3stap), probe::nfs.proc.commit(3stap),
probe::nfs.proc.read_setup(3stap), probe::nfs.proc.read_done(3stap), probe::nfs.proc.write_setup(3stap),
probe::nfs.proc.write_done(3stap), probe::nfs.proc.commit_setup(3stap), probe::nfs.proc.commit_done(3stap), probe::nfs.proc.open(3stap),
probe::nfs.proc.release(3stap), probe::nfs.proc.handle_exception(3stap), probe::nfs.proc.create(3stap), probe::nfs.proc.remove(3stap),
probe::nfs.proc.rename(3stap), stap(1), stapprobes(3stap)
IBM
--- tapset::nfs_proc(3stap)