Bug 1093909 - cannot unmount btrfs [NEEDINFO]
Summary: cannot unmount btrfs
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-03 08:24 UTC by Karel Volný
Modified: 2014-06-23 14:49 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-06-23 14:49:51 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)

Description Karel Volný 2014-05-03 08:24:19 UTC
Description of problem:
My filesystem had some problems. As btrfsck doesn't allow to check mounted filesystem (and booting into emergency mode doesn't have an option not to mount root), I have booted from Fedora 20 netinstall CD (x86_64), choosing rescue.
When I got a question about mounting the disk, I've chosen so, so that I wouldn't have to configure the encryption manually.
After getting to the shell, I did umount /mnt/sysimage/home (as /home was subvolume of /) and then I tried to do umount /mnt/sysimage
This has failed with some message about /mnt/sysimage being in use.
However, neither fuser showed anything using the directory nor the device node, neither lsof listed it as open ...

Version-Release number of selected component (if applicable):
Fedora 20 netinstall CD (x86_64)

How reproducible:
(tried once)

Steps to Reproduce:
1. install Fedora with btrfs
(I'm not sure how important was that it was on encrypted partition)
2. boot from install media choosing rescue
3. let the helper mount the btrfs partition
4. try to umount it

Actual results:
umount: /mnt/sysimage: target is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))


Expected results:
the filesystem gets unmounted

Additional info:

Comment 1 Justin M. Forbes 2014-05-21 19:37:58 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Justin M. Forbes 2014-06-23 14:49:51 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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