Why does system always prompts that /dev/sda1 is already mounted or mount point busy
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Why does system always prompts that /dev/sda1 is already mounted or mount point busy
Hi guys(girls),
The problem I encountered really annoyed me so much!
At first, I used "mount|grep sda1" to view whether the block device was mounted or not, it itemized many items about /dev/sda1, like this:
...
/dev/sda1 /mnt/eSata fuseblk rw,user_id=0,group_id=0,default_permissions,allow_other 0 0
/dev/sda1 /home/0common fuseblk rw,user_id=0,group_id=0,default_permissions,allow_other 0 0
/dev/sda1 /tmp/atalk fuseblk rw,user_id=0,group_id=0,default_permissions,allow_other 0 0
/dev/sda1 /tmp/albumcache fuseblk rw,user_id=0,group_id=0,default_permissions,allow_other 0 0
...
So, I performed "umount /dev/sda1" many times to umount the block device, but several items cannot be umounted,
the system prompts device is busy, like this :
umount: /tmp/minidlna: device is busy
So, I used "umount -l /dev/sda1" to lazily umount this device.
Secondly, I tried to mount /dev/sda1 , unfortunately, it always prompt me like this:
mount: /dev/sda1 already mounted or /mnt/ufsd busy
Then I used 'fuser /mnt/ufsd' to view which process accessing to this mount point ,but got nothing.
I want to mount /dev/sda1 to /mnt/ufsd, How can I work out this problem?
Any help and solutions are appreciated! Thank you all!
Last edited by chinabenjamin66; 09-30-2012 at 10:11 AM.
normally /dev/sda1 IS THE / partition ( like the windows c:\\ drive )
and is mounted on boot because the operating system is there
By the way, the linux I used is an embeded linux, its / partition is not /dev/sda1, /dev/sda is an external scsi disk used for testing.
As you can see below, it had been ever mounted on other mount point:
bash-3.2# mount|grep /sda1
/dev/sda1 on /mnt/eSata type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /home/0common type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /tmp/atalk type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
.....
====fisrt step========
bash-3.2# mount|grep sda1
/dev/sda1 on /mnt/eSata type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /home/0common type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /var/cache/mt-daapd type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /tmp/minidlna type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
====second step========
bash-3.2# umount /mnt/eSata
umount: /mnt/eSata: device is busy
umount: /mnt/eSata: device is busy
====third step=========
bash-3.2# fuser /mnt/eSata
Cannot stat /mnt/eSata: Transport endpoint is not connected
Cannot stat /mnt/eSata: Transport endpoint is not connected
Cannot stat file /proc/2113/fd/7: Transport endpoint is not connected
Cannot stat file /proc/2475/fd/3: Transport endpoint is not connected
Cannot stat file /proc/2475/fd/4: Transport endpoint is not connected
====forth step=========
bash-3.2# ps -ef|grep 2113
apache 2113 1 0 09:30 ? 00:00:00 mt-daapd
root 5213 4143 0 11:36 pts/0 00:00:00 grep 2113
====fifth step=========
bash-3.2# mount |grep sda1
/dev/sda1 on /mnt/eSata type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)
/dev/sda1 on /tmp/minidlna type fuseblk (rw,user_id=0,group_id=0,default_permissions,allow_other)ep
====sixth step=========
bash-3.2# fuser /mnt/eSata
Cannot stat /mnt/eSata: Transport endpoint is not connected
Cannot stat /mnt/eSata: Transport endpoint is not connected
bash-3.2# fuser /tmp/minidlna
Cannot stat /tmp/minidlna: Transport endpoint is not connected
Cannot stat /tmp/minidlna: Transport endpoint is not connected
So I want to know how to work out the problem of 'Transport endpoint is not connected'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.