- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- file system full
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
Forums
Discussions
Discussions
Discussions
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
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
10-09-2003 12:36 AM
10-09-2003 12:36 AM
file system full
Just got problem this station terminated and restart the application.
But after system recover, I run dmesg command and got file system full message.
When I check with bdf none of the Hdd partition shown 100% usage.
Can anybody tell me what to do?
Regards,
Ted
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 12:39 AM
10-09-2003 12:39 AM
Re: file system full
This may well have been a temporary condition. Either that or the process that is filling the file system is still running, still has the file open, and thus bdf can't see it. Are there any processes associated with this application that would be writing to this filesystem at this point?
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 12:42 AM
10-09-2003 12:42 AM
Re: file system full
It probably was full but restarting the application sorted the problem out. I would guess the application created a tempory file that filled up the filesystem and then removed it. This is common practice for tempory files and does not give you the space back until the application closes the file. When you restarted the applciation the space came back.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 12:43 AM
10-09-2003 12:43 AM
Re: file system full
The file system could have filled some time before and now bdf gives that it is not full.
check for the timestamp of those messages.
If those messges are recent then that application process is creating a huge temporary file on that file system which fills up the space.
you can use lsof to trace that application process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 12:45 AM
10-09-2003 12:45 AM
Re: file system full
You are telling that after system recover, the dmesg command gave file system full. Track the file system.
Check for any biggest files in that file system and try to run fuser on that.
HTH,
Umapathy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 12:53 AM
10-09-2003 12:53 AM
Re: file system full
did the restart and recover operation involve booting the machine?
If not, the dmesg message could be old, just stating that at a certain time a file system was full.
just guessing...
regards,
John K.