Check your /tmp it is temporary. It can get filled by a lot of processes. It is the default sas is using during the installation and may be more. Unix is having a convention for his hfs see: Filesystem Hierarchy Standard - Wikipedia, the free encyclopedia As being a convention you do not need to follow that it is just good practice to do so. There are a lot of folders with some dedicated meaning /tmp /home /opt /etc /var for /tmp (default system work) you have the split up of saswork on a different mountpoint (/var/saswrk?). it cannot interference with /tmp anymore for /home you could do that as /home (default unix system keys) /home/usrgrp1/<key> a split up s this mountpoint cannot interference with the system ones for /opt it are less or more stable types (not changing often) for installing applications. sas can be seen as a TI-application. this is according: /opt (The Linux Documentation Project) This one should have a dedicated mountpoint (or more) by that isolating it for all the rest, for /var (variable data) you see log-files This one should have a dedicated mountpoint (or more) by that isolating it for all the rest, If you read this than you can see SAS institute is putting a lot of rubbish in that SAS-config mapping. Process logging user databases user coding/programs all getting mixed up. I do not understand why do not follow the ideas of mountpoints and common Unix namings, that is something they should answer. (tlpd.org refrences) The possible most harmfull are all those loggings. You can redirect (logical link) / rename those to an other location eg /var/opt/saslog and put a own mountpoint on that. the dec/sdb1 is pointing to the name cubedata/lvcubdat1 94% more the association for cubes and not the sas software. that one is not full. I guess it is /tmp or /var being in problems. You have to validate that. Just adding the not fhs: Linux Directory Hierarchy: Oriented to the Software Parts The FHS is part of the LSB (Linux Standard Base), which makes him a good thing because all the industry is moving thowards it, and is a constant preoccupation to all distributions. FHS defines in which directories each peace of Apache, Samba, Mozilla, KDE and your Software must go, and you don't have any other reason to not use it while thinking in developing your Software, but I'll give you some more: FHS is a standard, and we can't live without standards This is the most basic OS organization, that are related to access levels and security, where users intuitively find each type of file, etc Makes user's life easyer This last reason already justifies FHS adoption, so allways use the FHS !!! More about FHS importance and sharing the same directory structure can be found in Red Hat website.
... View more
