Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Disk full on /usr/sap 1

Status
Not open for further replies.

SimonPeh

MIS
Sep 11, 2002
96
SG
Hi Guys,

I did a df -k and it seem the one of the disk on /usr/sap is almost full. And this is a SAP directory which I'm not familiar with.

P01_dom#usr_sap 4189184 3909851 279333 94% /usr/sap

Any idea how I can release/delete some file where it doesnt affect operation ?

Thanks for any advice.
 
Simon,

I think I'd start by looking for large files which appear to have filled up your filesystem. It could core files, log files or simply runaway processes that are writing to files uneccessarily. Do a:

find /usr -size +5000 -print (or -exec ls -la {} \; to get the date/time details for the file)

and a:

find /usr -name core -print

to discover the large files present in the filesystem (change +5000 to a larger number if the number of files found is large). You may be able to look at the files to see whether they can be trimmed (it is often a good idea to do this to log files anyway), thus releasing space on your system. Post back if you require more advice, including some details of the larger files if possible. Hope this helps to get you started.
 
Hi Ken,

Thanks for the tips. It really do retrieve a lot of files


# find /usr -name core -print
/usr/users/p01adm/core
/usr/sap/P01/D01/work/core

And the most are this core file
-rw------- 1 p01adm sapsys 897343488 Jul 28 01:03 core

which occupied a lot of space ... still no idea of wat does this core file foes .. so do not dare to delete or change anything.

 
On the face of it it appears that one of your users has hit a problem with something they were doing and his has caused the system to hiccup and create the core file (some size it is too!). Generally speaking, these files are used by system suppliers to analyse what happened, but if it's not happening on a regular basis it's probably saf to delete it. You could ask the user if they remember a problem which might have caused the core file (you'll be lucky if they admit it, however!). I see it was created at 01:03. Is that a time when a backup or similar kicks in?

If you do a strings core on the file, this may give you an indication of the program which caused it. If you want to save it just in case, are you able to archive it to tape then delete it?

HTH.
 
Yes. It started backup around 0100 hr.
Anyway Ihave arhive it as a gz file and have recover abt 30% of the disk space.

Hopefully, it doesnt impact the system.

And thanks for the help. Really Appreciated !
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top