- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- umount of a normal filesystem weirdly failed
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
04-10-2002 12:22 AM
04-10-2002 12:22 AM
I encountered a strange question.
One day I found one normal file system 100% then I went into the mount point and used the command 'du -xk .' to list the usage situation but I found the used size is far less than the total size but the result of 'df -k' showed the filesystem was full. I used 'du -r .' to check whether there was any files could not be opened but no errors found.
Then I decided to umount the filesystem and remount it in order to make system update the information. But I failed to umount this filesystem although I used 'fuser -kc mount_point ' and 'fuser -ku special_file_name ' to kill any user using the file system. I was always told 'Device Busy' by the system. So I think it is a little difficult to explain what possess the rest blocks of this filesystem.
Could you give me any reasonable explanation or solution ? Thanks a lot!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:27 AM
04-10-2002 12:27 AM
Re: umount of a normal filesystem weirdly failed
Was it a vg00 file system?
Gideon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:30 AM
04-10-2002 12:30 AM
Re: umount of a normal filesystem weirdly failed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:38 AM
04-10-2002 12:38 AM
Re: umount of a normal filesystem weirdly failed
Please forgive if i'm incorrect, but your current directory at the time of attempting to action the umount was the actual 'mount point?'
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:42 AM
04-10-2002 12:42 AM
Re: umount of a normal filesystem weirdly failed
Certainly.
Thanks
Albert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:53 AM
04-10-2002 12:53 AM
Re: umount of a normal filesystem weirdly failed
Sorry,
If you were in the mount point at the time of attempting you umount you would get the message device busy. You need to be in the root (/) directory
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 12:54 AM
04-10-2002 12:54 AM
Re: umount of a normal filesystem weirdly failed
Certainly I am in the '/' directory.
Thanks.
Albert
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 01:08 AM
04-10-2002 01:08 AM
SolutionThere could be some process writing into that filesystem and whose open file pointers no longer exist. Check it using lsof . Free download from
http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.61/
That will give some clue on what processes are writing into the filesystem.
Another reason why it may not be unmounting could be because it has a nested mount. You can verify this by running
bdf | grep "mountpoint" .
HTh
raj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2002 01:19 AM
04-10-2002 01:19 AM
Re: umount of a normal filesystem weirdly failed
I think you are right and I will try as you told me. Thanks a lot!
Albert