Subject: Re: mosaic problem
To: None <abs@netbsd.org>
From: Daniel Senderowicz <daniel@synchrods.synchrods.COM>
List: port-pmax
Date: 01/17/2000 11:43:01
Here are the setups:

/etc/fstab:

/dev/rz0a / ffs rw 1 1
/dev/rz0b none swap sw 0 0
/dev/rz0d /usr ffs rw 1 2
/kern /kern kernfs rw

# df -k
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/rz0a       31469    24039     5856    80%    /
/dev/rz0d     8282050   517320  7350627     6%    /usr
kernfs              1        1        0   100%    /kern

# df -k /var/tmp
Filesystem  1K-blocks     Used    Avail Capacity  Mounted on
/dev/rz0a       31469    24040     5855    80%    /

>	Is the one with the problem running on a partition with
>	more than 2GB free?
>
>
>		David/absolute
>
>On Mon, 17 Jan 2000, Daniel Senderowicz wrote:
>
>> Hi folks,
>> 
>> I'm struggling with a problem with mosaic. Here it goes:
>> 
>> I have 1.4.1 (with the 1.4.2_ALPHA kernel) and 1.4.2_ALPHA in
>> two identical machines DECStation 5000/240 with the same disks
>> (9.1GB). The mosaic version already compiled is 2.7b5. I
>> installed it on these machines at different times, within a few
>> weeks of difference.  The problem that I'm having is that the
>> one that I installed first (with 1.4.1) keeps giving me at the
>> bottom of the window a message saying:
>> 
>> "Can't open temporary file -- Serious Problem".
>> 
>> and
>> 
>> "Insufficient temporary disk space; could not transfer data"
>> 
>> Disk space is not really a problem in this machine, unless
>> mosaic is trying to write big stuff in the root partition where
>> I have 62k blocks. However I have the same in the machine that
>> is working OK. I couldn't find what could be different between
>> the two machines that makes this to happen.  Nor I don't know
>> where is mosaic trying to write in order to check in that area.
>> 
>> I will appreciate any pointers.
>> 
>> Dan
>> 
>
>