[BusyBox 0001550]: mount: mounting /dev/sda2 on /mnt/sda2 failed: Device or resource busy

bugs at busybox.net bugs at busybox.net
Thu Oct 25 17:48:02 UTC 2007


The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=1550 
====================================================================== 
Reported By:                jordon liu
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1550
Category:                   New Features
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     closed
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             10-22-2007 21:07 PDT
Last Modified:              10-25-2007 10:48 PDT
====================================================================== 
Summary:                    mount: mounting /dev/sda2 on /mnt/sda2 failed:
Device or resource busy
Description: 
hi,
I have port the fuse2.7 and ntfsprogs2.0.0 to the arm platform, base the
Montavista linux kernel of 2.6.10 .
it can mkntfs /dev/sda2 successfully,but when I run the command:
ntfsmount /dev/sda2 /mnt/sda2,it complains that: 
# ntfsmount /dev/sda2 /mnt/sda2
mount: mounting /dev/sda2 on /mnt/sda2 failed: Device or resource busy
fuse_mount failed.
Unmounting /dev/sda2 ()
#

and I port the ntfs-3g to the arm , run the command still get the result:
# ./ntfs-3g /dev/sda2 /mnt/sda2
mount: mounting /dev/sda2 on /mnt/sda2 failed: Device or resource busy
Unmounting /dev/sda2 ()
# 

but I just use the mount /dev/sda2 /mnt/sda2 is succeed. 

and my other command use busybox1.2.4, but the mount/umount use the
busybox 1.7.4,
since the ntfsmount and ntfs-3g would call mount function, and the "Device
or resource busy" was printed by busybox, so maybe the problem was exist at
busybox?

====================================================================== 

---------------------------------------------------------------------- 
 vda - 10-24-07 10:49  
---------------------------------------------------------------------- 
> # ntfsmount /dev/sda2 /mnt/sda2
> mount: mounting /dev/sda2 on /mnt/sda2 failed: Device or resource busy
> fuse_mount failed.
> Unmounting /dev/sda2 ()

ntfsmount is not a part of busybox. Is it a shell script which calls
busybox's mount?

> # ./ntfs-3g /dev/sda2 /mnt/sda2
> mount: mounting /dev/sda2 on /mnt/sda2 failed: Device or resource busy
> Unmounting /dev/sda2 ()

Same question - does it use busybox's mount?

> since the ntfsmount and ntfs-3g would call mount function, and the
"Device or
> resource busy" was printed by busybox, so maybe the problem was exist
at
> busybox?

What do you mean by "mount function"? C function? Or do you mean "...would
call busybox command"? 

---------------------------------------------------------------------- 
 jordon liu - 10-24-07 23:37  
---------------------------------------------------------------------- 
sorry, the problem has no relation to busybox.

it is my hard disk have problem,and it has no problem after I change a new
hard disk.

ntfsmount is a project based on busybox and fuse, but it doesn't use c
funtion to call busybox mount.c directly.

thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-22-07 21:07  jordon liu     New Issue                                    
10-22-07 21:07  jordon liu     Status                   new => assigned     
10-22-07 21:07  jordon liu     Assigned To               => BusyBox         
10-24-07 10:49  vda            Note Added: 0002860                          
10-24-07 10:49  vda            Status                   assigned => feedback
10-24-07 23:37  jordon liu     Note Added: 0002861                          
10-25-07 10:48  vda            Status                   feedback => closed  
======================================================================




More information about the busybox-cvs mailing list