[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20001201: McIDAS: memory allocation problem (cont.)

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20001201: McIDAS: memory allocation problem (cont.)
  • Date: Fri, 01 Dec 2000 15:41:11 -0700
>From: Gary Cunning <address@hidden>
>Organization: NCAR/RAP
>Keywords: 200011061722.eA6HMI408974 GOES imagery

Gary,

>My computer has 512 MB ram. My computer's swap space is at 128 MB. I
>think most of the problem is that my computer's shared memory space is
>only 33 MB.

This could be the problem all right.

>have plenty of disk space. For example:
>
>(raven) notes 274 % df
>Filesystem         1024-blocks  Used Available Capacity Mounted on
>/dev/sda2            1018329  482891   482826     50%   /
>/dev/sda3            2035638 1532224   398189     79%   /home
>/dev/sda4            10037823  257747  9259169      3%   /raven_data1
>/dev/sdb2            3044019  144058  2742524      5%   /raven_dev
>/dev/sdb3            5437453  230429  4925485      4%   /raven_data2
>
>
>I am working on increasing my computers swap space and shared memory to
>256 MB. I will take a look at the email archives to see if anything
>there is helpful.

You can also look in:

http://www.unidata.ucar.edu/packages/mcidas/770/mcx/workstation.html

At the bottom of this page are a couple of options for increasing shared
memory in Linux.

>From address@hidden Fri Dec  1 11:57:59 2000
>
>Here is some more information you requested, the file sizes and memory
>size.
>
>(raven) VIS4KM2 297 % ls -l
>total 17884
>-rw-rw-r--   1 mcidas   users     4558736 Nov 21 10:02
>VIS4KM2_20001121_1645
>-rw-rw-r--   1 mcidas   users     4558736 Nov 21 10:30
>VIS4KM2_20001121_1715
>-rw-rw-r--   1 mcidas   users     4558736 Nov 21 11:02
>VIS4KM2_20001121_1745
>-rw-rw-r--   1 mcidas   users     4558736 Nov 21 11:30
>VIS4KM2_20001121_1815
>(raven) VIS4KM2 298 % cat /proc/meminfo
>        total:    used:    free:  shared: buffers:  cached:
>Mem:  529555456 500776960 28778496 73146368 354496512 52215808
>Swap: 133885952  4603904 129282048
>MemTotal:    517144 kB
>MemFree:      28104 kB
>MemShared:    71432 kB
>Buffers:     346188 kB
>Cached:       50992 kB
>SwapTotal:   130748 kB
>SwapFree:    126252 kB

This shows that you have about 70 MB of shared memory, and that almost
all of your physical memory is gone.  What the heck is running?

>One more thing, earlier in the week when I was playing with mcidas I was
>able to run the IMGREMAP command. At one point I ran a command that
>caused a segment violation. I cant't remember what the name of the
>command. Since that time I have had the memory problems. Is there some
>kind of lock file for shared memory that mcidas refers to before trying
>to allocate more memory?

No, but there are lock files for McIDAS sessions in /tmp/mclock.

Tom