filesystems with 100%

[Carme Torca]

Hi,

This morning I had one filesystem with 64728 Kbytes available space:

/dev/vgPRD/sapdata3 28262400 28197168 64728 100% 24 2024 1% /oracle/PRD/sapdata3

but now is with 0 kbytes

Filesystem kbytes used avail %used Mounted on
/dev/vgPRD/sapdata3 28262400 28262400 0 100% /oracle/PRD/sapdata3

In this filesystem there are only sap files:

-rw-rw---- 1 oraprd dba 8388616192 Jan 10 17:14 ./prd_3/prd.data3
-rw-rw---- 1 oraprd dba 8388616192 Jan 10 17:14 ./prd_7/prd.data7
-rw-rw---- 1 oraprd dba 2097160192 Jan 10 17:13 ./prd_11/prd.data11
-rw-rw---- 1 oraprd dba 3221233664 Jan 10 17:14 ./prd46c_3/prd46c.data3
-rw-rw---- 1 oraprd dba 4194312192 Jan 10 14:06 ./temp_1/temp.data1
-rw-rw---- 1 oraprd dba 2044723200 Jan 10 17:14 ./prd_15/prd.data15
-rw-rw---- 1 oraprd dba 2044723200 Jan 10 17:14 ./prd_35/prd.data35
-rw-rw---- 1 oraprd dba 1258283008 Jan 10 17:09 ./prd_38/prd.data38
-rw-rw---- 1 oraprd dba 650117120 Jan 10 17:09 ./prd_39/prd.data39

and are the same and with the same space that this morning.

I have only this question. What there are in this filesytem that this morning was with 64728 Kbytes available and now it has 0 Kbytes available?

Thanks a lot of!
Carmen.

[Coolmar]

You will have to comb through that filesystem and look for something out of the ordinary .... unusually huge files, or many files that aren't like the others. You can do an "ls -ltr" on the directory to find the most recent files. I have also attached a script (that I got from this forum) that I use for this type of thing all the time. It will tell you exactly how big each directory within a filesystem is and helps you to narrow down the problem.

HTH,
Sally

[Nobody's Hero]

Look close. sometimes there is a .filename or dir. that holds a lot of bytes, sometimes. like a .mozilla

Just a thought.

[Bill Hassell]

This is a 28 Gb directory so 64 megs is a VERY small part of the directory. I am assuming that the above listing is all there is in the directory. Now two things could have happened:

1. Your application opened one of the files nad made it slightly larger.

2. The files are for your database and were created as sparse files. This means that there are undefined records and no space is required for these undefined records. However, the database added new records inside the file and additional space was required. This is the most likely scenario.

The fact that the space available is exactly 0 probably means that your application had an error when it ran out of space. The bottom line is that you need a *LOT* more free space than 64 megs. Extend the lvol to 29 or 30 Gb and watch for growth.

[Roboz]

Hola Carmen COmo estas..

May I suggest the following:
Find out the content of the directories using the DU command or perhaps the FIND command a follows

du (in 512K blocks)
du -k (in kilobytes)

find -size +-exec ll {} \;

(notic e the "c" at the end and that I have split the command in two lines with a "\")

This will enable to identify large files and then you could ask your DBA to tell you what kind of data it is.


Espero que esto le ayude.. :-)