- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- umount problem
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
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
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
02-19-2003 04:26 AM
02-19-2003 04:26 AM
umount problem
While umounting FS it is giving the below error message :-
umount:cannot umount
Any suggestions.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 04:34 AM
02-19-2003 04:34 AM
Re: umount problem
Wrong device being used
see first char of ll
This is block
ll /dev/dsk/c0t6d0
brw-r----- 1 bin sys 31 0x006000 Dec 30 1999 /dev/dsk/c0t6d0
This is character
ll /dev/rdsk/c0t6d0
crw-r----- 1 bin sys 188 0x006000 Jun 21 1999 /dev/rdsk/c0t6d0
Always use /dev/dsk and not rdsk
Steve Steel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 04:40 AM
02-19-2003 04:40 AM
Re: umount problem
could you post a bdf and the command you have used.
try to use the
# umount /dev/vg00/lvol10
and fill in the number for vg and lv yourself.
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 04:40 AM
02-19-2003 04:40 AM
Re: umount problem
If it is mounted then just use
#umount
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 04:45 AM
02-19-2003 04:45 AM
Re: umount problem
# mount | grep /
Try to mount the filesystem and re-try to umount it.
Please also check the /etc/mnttab if the filesystem is in. Try this:
# mv /etc/mnttab /etc/mnttab.old
# mount -a
Hope that helps.
Regards ...
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 04:51 AM
02-19-2003 04:51 AM
Re: umount problem
Actually you've received an error:
[ENOTBLK] - name is not a block special device
Maybe you used a wrong FS-name?
Show results from:
#bdf
and
#cat /etc/mnttab
,please.
Rgrds.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 05:20 AM
02-19-2003 05:20 AM
Re: umount problem
Everything about mounting the FS was fine.
Mount was done using block device only but
by mistake it got mounted on wrong mount point.
Now it is not allowing me to umount it and in the fstab it has the correct entry. ( I mean mount point ).
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 05:27 AM
02-19-2003 05:27 AM
Re: umount problem
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 05:30 AM
02-19-2003 05:30 AM
Re: umount problem
can you umount the lvol instead of the /mountpoint ?
Robert-Jan.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 05:30 AM
02-19-2003 05:30 AM
Re: umount problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 05:33 AM
02-19-2003 05:33 AM
Re: umount problem
You can find this processes by following commands:
# fuser (-k) /
# lsof /
'lsof' can be downloaded by following URL:
http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.64/
Only if you are not able to stop/kill the processes which keep the filesystem busy you have to reboot.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 06:24 AM
02-19-2003 06:24 AM
Re: umount problem
I have already tried all the options suggested above but it doesn't work.
So, I think Pete Randall is right, I have no other option then to reboot the server.
Anyway, thanks for all the comments.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 06:47 AM
02-19-2003 06:47 AM
Re: umount problem
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 06:51 AM
02-19-2003 06:51 AM
Re: umount problem
He wasn't getting a "device busy".
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 08:36 AM
02-19-2003 08:36 AM
Re: umount problem
Pete is right , FS is not busy but still I had the problem.
Anyway, once I reboot it will be fine.
Lets hope we will have some soln. in future for such problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2003 10:50 AM
02-19-2003 10:50 AM
Re: umount problem
I am sure you should not have to reboot for just unmounting a filesystem and that too if it is not busy. And also, if it got mounted on the wrong mount point your application also will not use this and thus no possibility of some open system calls for this mount point.