From: Ian on
Hi,
I am attempting to install Oracle 10g on Solaris 10x86.
When I run the installer I get a "error in writing to directory
/tmp/oraInstall... ..." asks me it ensure there is enough disk space and
directory is writable and greater than 68mb.
But the df -h /tmp tells me I have 1014M and available 953M
Any help as to what to do next appreciated?
regards
Ian


From: Jay G. Scott on
In article <422738b3_4(a)news.chariot.net.au>, Ian <not(a)available.com.au> wrote:
>Hi,
>I am attempting to install Oracle 10g on Solaris 10x86.
>When I run the installer I get a "error in writing to directory
>/tmp/oraInstall... ..." asks me it ensure there is enough disk space and
>directory is writable and greater than 68mb.
>But the df -h /tmp tells me I have 1014M and available 953M
>Any help as to what to do next appreciated?
>regards
>Ian
>
>

if tmp is not a separate filesystem then it it part of swap.
if swap is using most of the space.....
if you didn't ask for a separate /tmp explicitly, the default
is to share 'em.

i almost always make a separate official partition for /tmp.
df -h /tmp tells me the truth, not sure if that's true if
it's used for swap, too.

also, you could have some huge files open, that take up space
but don't get detected by df (or du, IIRC). maybe fuser will
find those. that hasn't happened to me in a while.


j.


--
Jay Scott 512-835-3553 gl(a)arlut.utexas.edu
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div. S224
University of Texas at Austin
From: Klaus-Dieter Ost on
Jay G. Scott schrieb:
> also, you could have some huge files open, that take up space
> but don't get detected by df (or du, IIRC). maybe fuser will
> find those. that hasn't happened to me in a while.

A file could be deleted on disk (i.e. there's no directory entry for
it), but could still be held open by one or more processes. This means
that there's still an inode and some disk blocks allocated for this
file. These blocks will add up to the used blocks of the df command, but
they will not show up in the du command. The former counts disk blocks,
the latter searches the directory hierarchy. fuser can not report the
file, because there's no directory entry.

E.g.:

$ df -k .
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s6 13698171 3628239 9932951 27% /export/home
$ mkfile 100m oops
$ df -k .
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s6 13698171 3730703 9830487 28% /export/home
$ ls -i oops
2718 oops
$ sleep 99999 <oops &
[1] 16920
$ rm oops
$ df -k .
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s6 13698171 3730703 9830487 28% /export/home
$ pfiles 16920
16920: sleep 99999
Current rlimit: 256 file descriptors
0: S_IFREG mode:0600 dev:136,6 ino:2718 uid:2005 gid:2001 size:104857600
.... omitted ...
$ kill 0
[1] + Terminated sleep 99999 <oops &
$ df -k .
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s6 13698171 3628240 9932950 27% /export/home
$


Hope, that helps to clarify - have a nice day,

Klaus

--
------------------------------
Dipl.-Inform. Klaus-Dieter Ost
kdo(a)no-spam-to-smo.de

Unix Solaris AIX - C++ Java sh
Software Design Documentation
------------------------------