Bug 1159648 - umount /usr failed, because /usr is busy on boot time
Summary: umount /usr failed, because /usr is busy on boot time
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-02 16:39 UTC by Sergei LITVINENKO
Modified: 2015-06-29 23:07 UTC (History)
16 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 23:07:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
journalctl -b full output (29.49 KB, application/x-bzip)
2014-11-03 18:29 UTC, Sergei LITVINENKO
no flags Details
lsblk output (880 bytes, text/plain)
2014-11-03 18:31 UTC, Sergei LITVINENKO
no flags Details
/etc/fstab (1.47 KB, text/plain)
2014-11-03 18:34 UTC, Sergei LITVINENKO
no flags Details

Description Sergei LITVINENKO 2014-11-02 16:39:14 UTC
Description of problem:
after update systemd, a lot of error about umount /usr failed, because /usr is busy on boot time

Version-Release number of selected component (if applicable):

systemd-208-25.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Boot system
2. Look on console
3. Look into /var/messages

Actual results:
boot with a lot of error messages about /usr is busy and umount is not possible

Expected results:


Additional info:

Nov  2 18:15:59 homedesk kernel: RPC: Registered named UNIX socket transport module.
Nov  2 18:15:59 homedesk kernel: RPC: Registered udp transport module.
Nov  2 18:15:59 homedesk kernel: RPC: Registered tcp transport module.
Nov  2 18:15:59 homedesk kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Nov  2 18:15:59 homedesk umount: umount: /usr: target is busy
Nov  2 18:15:59 homedesk umount: (In some cases useful info about processes that
Nov  2 18:15:59 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:15:59 homedesk systemd: usr.mount mount process exited, code=exited status=32
Nov  2 18:15:59 homedesk systemd: Failed unmounting /usr.
Nov  2 18:15:59 homedesk systemd: Unit usr.mount is bound to inactive service. Stopping, too.
Nov  2 18:15:59 homedesk systemd: Unmounting /usr...
Nov  2 18:15:59 homedesk umount: umount: /usr: target is busy
Nov  2 18:15:59 homedesk umount: (In some cases useful info about processes that
Nov  2 18:15:59 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:15:59 homedesk systemd: usr.mount mount process exited, code=exited status=32
Nov  2 18:15:59 homedesk systemd: Failed unmounting /usr.
Nov  2 18:15:59 homedesk systemd: Unit usr.mount is bound to inactive service. Stopping, too.
Nov  2 18:15:59 homedesk systemd: Unmounting /usr...
Nov  2 18:15:59 homedesk umount: umount: /usr: target is busy
Nov  2 18:15:59 homedesk umount: (In some cases useful info about processes that
Nov  2 18:15:59 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:15:59 homedesk systemd: usr.mount mount process exited, code=exited status=32
Nov  2 18:15:59 homedesk systemd: Failed unmounting /usr.
Nov  2 18:15:59 homedesk systemd: Unit usr.mount is bound to inactive service. Stopping, too.
Nov  2 18:15:59 homedesk systemd: Unmounting /usr...
Nov  2 18:15:59 homedesk umount: umount: /usr: target is busy
Nov  2 18:15:59 homedesk umount: (In some cases useful info about processes that
Nov  2 18:15:59 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:15:59 homedesk systemd: usr.mount mount process exited, code=exited status=32
Nov  2 18:15:59 homedesk systemd: Failed unmounting /usr.
Nov  2 18:15:59 homedesk systemd: Unit usr.mount is bound to inactive service. Stopping, too.
Nov  2 18:15:59 homedesk systemd: Unmounting /usr...
Nov  2 18:15:59 homedesk umount: umount: /usr: target is busy
Nov  2 18:15:59 homedesk umount: (In some cases useful info about processes that
Nov  2 18:15:59 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:15:59 homedesk systemd: usr.mount mount process exited, code=exited status=32
Nov  2 18:15:59 homedesk systemd: Failed unmounting /usr.
Nov  2 18:15:59 homedesk systemd: Unit usr.mount is bound to inactive service. Stopping, too.
Nov  2 18:15:59 homedesk systemd: Unmounting /usr...

...
... skip
...

Nov  2 18:16:01 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:01 homedesk kernel: sound hdaudioC0D0: autoconfig: line_outs=4 (0x12/0x16/0x24/0x25/0x0) type:line
Nov  2 18:16:01 homedesk umount: (In some cases useful info about processes that
Nov  2 18:16:01 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:16:01 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:01 homedesk kernel: sound hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Nov  2 18:16:01 homedesk kernel: sound hdaudioC0D0:    hp_outs=1 (0x11/0x0/0x0/0x0/0x0)
Nov  2 18:16:01 homedesk kernel: sound hdaudioC0D0:    mono: mono_out=0x0
Nov  2 18:16:01 homedesk kernel: sound hdaudioC0D0:    dig-out=0x1b/0x0
Nov  2 18:16:02 homedesk kernel: sound hdaudioC0D0:    inputs:
Nov  2 18:16:02 homedesk kernel: sound hdaudioC0D0:      Front Mic=0x14
Nov  2 18:16:02 homedesk kernel: sound hdaudioC0D0:      Rear Mic=0x17
Nov  2 18:16:02 homedesk kernel: sound hdaudioC0D0:      Line=0x15
Nov  2 18:16:02 homedesk kernel: sound hdaudioC0D0:      CD=0x18
Nov  2 18:16:02 homedesk umount: (In some cases useful info about processes that
Nov  2 18:16:02 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:16:02 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:02 homedesk umount: umount: /usr: target is busy
Nov  2 18:16:02 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:02 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:02 homedesk umount: umount: /usr: target is busy
Nov  2 18:16:02 homedesk umount: (In some cases useful info about processes that
Nov  2 18:16:02 homedesk umount: use the device is found by lsof(8) or fuser(1).)
Nov  2 18:16:02 homedesk systemd: Failed unmounting /usr.
Nov  2 18:16:02 homedesk kernel: input: HDA Intel Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5

Comment 1 Zbigniew Jędrzejewski-Szmek 2014-11-02 18:04:42 UTC
Please post pull 'journalctl -b' output from a failed boot, and from a working boot if possible, and /etc/fstab and lsblk output.

Comment 2 Zbigniew Jędrzejewski-Szmek 2014-11-02 18:05:03 UTC
s/pull/full/

Comment 3 Sergei LITVINENKO 2014-11-03 18:29:48 UTC
Created attachment 953217 [details]
journalctl -b full output

full journalctl -b output

Comment 4 Sergei LITVINENKO 2014-11-03 18:31:28 UTC
Created attachment 953218 [details]
lsblk output

output of lsblk

Comment 5 Sergei LITVINENKO 2014-11-03 18:34:01 UTC
Created attachment 953219 [details]
/etc/fstab

/etc/fstab

Comment 6 Zbigniew Jędrzejewski-Szmek 2014-11-04 02:21:39 UTC
So, systemd vehemently tries to unmount /usr. I'd guess that this is because of the hard-coded handling of /usr in some place, but this is rather surprising. Looks like a bug definitely.

Comment 7 Rob 2014-11-06 02:54:52 UTC
Exactly same problem here with "systemd-208-26.fc20.x86_64"

R.

Comment 8 Sergei LITVINENKO 2014-11-06 18:10:15 UTC
>> Exactly same problem here with "systemd-208-26.fc20.x86_64"

Yes,
the same

Comment 9 Niranjan Mallapadi Raghavender 2014-11-17 05:49:29 UTC
Any workarounds on this issue ?

Comment 10 pkoz 2014-11-22 10:52:33 UTC
The same umount /usr problem at boot with systemd.x86_64 208-28.fc20

Comment 11 jean-pierre cartal 2014-11-25 07:37:18 UTC
Same problem for me here with systemd-208-28.fc20.i686

Comment 12 Sergei LITVINENKO 2015-01-10 11:36:21 UTC
The same problen for systemd-208-28.fc20.x86_64

Comment 13 pkoz 2015-02-21 21:12:32 UTC
Still the same thing with systemd-208-30.fc20.x86_64.

Comment 14 Sergei LITVINENKO 2015-02-21 21:35:28 UTC
>> systemd-208-30.fc20.x86_64

Yes, the same. Issue is not solved.

Comment 15 Marek Pikuła 2015-04-27 18:34:25 UTC
Same there on systemd-219. Additionally it tries to umount /opt

Comment 16 Marek Pikuła 2015-05-06 09:52:18 UTC
It seems like it's gone now in systemd-219_p112.

Comment 17 Fedora End Of Life 2015-05-29 13:12:21 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 18 Fedora End Of Life 2015-06-29 23:07:38 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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