Bug 523436 - Filesystem seems busy even if no access it
Summary: Filesystem seems busy even if no access it
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: util-linux-ng
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Karel Zak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 523164
TreeView+ depends on / blocked
 
Reported: 2009-09-15 13:58 UTC by Pavel Alexeev
Modified: 2009-12-07 09:59 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-12-07 09:59:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pavel Alexeev 2009-09-15 13:58:57 UTC
Description of problem:
[root@hubbitus temp]# umount /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root
umount: /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))
[root@hubbitus temp]# fuser -m /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root
[root@hubbitus temp]# fuser -km /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root
[root@hubbitus temp]# lsof | grep imgcreate-jH8Dyp
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/pasha/.gvfs
      Output information may be incomplete.
[root@hubbitus temp]# umount /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root
umount: /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))


# mount | grep imgcreate-jH8Dyp
/dev/loop0 on /home/pasha/temp/Fedora-korda/tmp/imgcreate-jH8Dyp/install_root type ext4 (rw)

Version-Release number of selected component (if applicable):
# rpm -q util-linux-ng
util-linux-ng-2.14.2-9.fc11.i586

How reproducible:
Always.

Steps to Reproduce:
It is loop mounted image in livecd-creator ( https://bugzilla.redhat.com/show_bug.cgi?id=523164 ).

Comment 1 Karel Zak 2009-12-07 09:59:26 UTC
The error EBUSY is usually generated by kernel, try 

   # strace -o ~/umount.log umount <mountpoint>
   # $EDITOR ~/umount.log

to see more details. The umount(8) is a simple wrapper around the umount syscall only. I guess there is any process that access the filesystem or so.

Please, check it with F-12 and reopen if the problem is still reproducible.


Note You need to log in before you can comment on or make changes to this bug.