- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Inode problem?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 11:11 AM
тАО11-26-2002 11:11 AM
Inode problem?
I am not certain this is the problem. If I have it wrong, pls let me know.
Thanks,
Mike
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 12:36 PM
тАО11-26-2002 12:36 PM
Re: Inode problem?
I would recommend that once you get the space issue resolved, reboot the system to clear up any potential problems.
Remember: before deleting any logs, stop any processes that are writing to the logs. Otherwise, the directory entry is gone, but the file is still allocated until all processes writing to it have stopped.
HTH
Marty
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 01:09 PM
тАО11-26-2002 01:09 PM
Re: Inode problem?
/var hosts lots of logs for various system activites specially /var/tmp which is used bu oracle /applicatiuons as a scrtach pad , all you do is
1. check /var/tmp
2. ls -lR /var | grep log
to know which log files have to be trimmed .
this will give back most of the space I assume you ahcve cleared all core files.
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 01:54 PM
тАО11-26-2002 01:54 PM
Re: Inode problem?
Deleting log files is not sufficient. If the processes that opened the files are still active, you won't get the space. For ex., if you cleared mail.log or syslog.log, you would need to restart syslogd.
You can use "lsof" to find out the processes and the opened files in a file system. Based on it you can clean up. You can get lsof 64bit from the following site.
ftp://ftp.fu-berlin.de/pub/unix/tools/lsof/binaries/hpux/B.11.00/vxfs/64/9000_800/
Also, /var/adm/sw/save contains saved patches. You can use "cleanup" command to delete lower versions of patches. Look at the man page of cleanup command. It is recommended to take a backup of /var/adm/sw/save before running the command. I would not suggest going any less than level 2.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 01:57 PM
тАО11-26-2002 01:57 PM
Re: Inode problem?
Hope this helps
nancy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 02:07 PM
тАО11-26-2002 02:07 PM
Re: Inode problem?
du -k /var | sort -rn | more
This tells me where all of the disk space is being used. Because a lot of little files can be just as big of a problem as a couple of big files. Now in the case of /var, you will probably have a bunch in /var/adm/sw and you might try a cleanup but DO NOT clean up first. Cleanup is something you do when you are not in a panic situation and you have made an archive of /var/adm/sw so you can roll back patches if needed.
You have to determine which processes own which files. I do this with fuser and make a determination of what needs to be trimmed or if the process can be terminated gracefully thereby giving up the space. If they are log files and you think you need to trim them, the best way to zero them out is with:
> log.file
It is just redirecting nothing to the file. This will zero the file and recover the space and the process that is logging to it doesn't have to stop and restart.
Good luck
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 06:48 PM
тАО11-26-2002 06:48 PM
Re: Inode problem?
live free or die
harry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2002 07:15 AM
тАО11-27-2002 07:15 AM
Re: Inode problem?
You can run bdf -i and see how many free inodes you have.
In some cases you do not see space released immediately after deleting the file, due to the different reasons, like file being locked by the process writing to it, etc.
We saw on our site this - huge file deleted and you still had 100% utilization of you file system.
There are few ways to force inode table to be refreshed. Easiest is to touch file in the file system. You can run sync as well.
Agree with the note that you might have process(es) filling up your logs VERY fast, therefore lsof is a good idea mentioned hereabove.
You might in this case consider reseting logs, like
> logfile.log
And of course some patches may be commited, so their uninstall information is removed from /var/adm/sw.
Hope this helps,
0leg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-27-2002 01:47 PM
тАО11-27-2002 01:47 PM
Re: Inode problem?
When a program (process) opens a file, it uses a file dicriptor.
If you delete the file, and the process is still running. The space is not released until the file descriptor is closed. This is usually done by killing the process.
Commonly, I have seen new admins rm /var/adm/syslog/syslog.log inorder ot free space.
The problem is that the space will not be freed until syslogd is stopped.
"fuser" might have found your problem for instance
fuser -u /dev/vg00/lvol4 (which is my /tmp) You would find what processes have files opened in tmp. Which would hopefully give you a clue to the errant program.
When removing\reduceing logfiles. It is a good practice to do a fuser on the file to see if it is has attached processes. If this is the case ZERO out or truncate the file instead of removeing it
(echo "" > badlog )
Rory