Volker A. Brandt wrote:
>>> So they only work on and off. I never bothered to find out what the
>>> problem was (in fact, I hadn't even tried the ramdiskadm cmd in that
>>> version of Solaris before this email thread showed up).
>>>
>> AIUI, the memory assigned to a ramdisk must be contiguous.
>>
> > So they only work on and off. I never bothered to find out what the
> > problem was (in fact, I hadn't even tried the ramdiskadm cmd in that
> > version of Solaris before this email thread showed up).
> >
>
> AIUI, the memory assigned to a ramdisk must be contiguous.
> This makes some sense in
Volker A. Brandt wrote:
>>> [most people don't seem to know Solaris has ramdisk devices]
>>>
>> That is because only a select few are able to unravel the enigma wrapped in
>> a clue that is solaris :)
>>
>
> Hmmm... very enigmatic, your remark. :-)
>
>
> However, in this case I suspect
> Note this from vmstat(1M):
>
> Without options, vmstat displays a one-line summary of the
> virtual memory activity since the system was booted.
Oops, you're correct. I was only trying to demonstrate that there
was ample free memory and ramdiskadm just didn't work. Usually I do
tha
On Mon, Sep 29, 2008 at 2:12 AM, Volker A. Brandt <[EMAIL PROTECTED]> wrote:
> kthr memorypagedisk faults cpu
> r b w swap free re mf pi po fr de sr lf lf lf s0 in sy cs us sy id
> 0 0 0 33849968 2223440 2 14 1 0 0 0 0 0 21 0 21 813 1
> > [most people don't seem to know Solaris has ramdisk devices]
>
> That is because only a select few are able to unravel the enigma wrapped in a
> clue that is solaris :)
Hmmm... very enigmatic, your remark. :-)
However, in this case I suspect it is because ramdisks don't really
work well on
