Bug 1359423 - NFS failed to be unmounted when shutdown
Summary: NFS failed to be unmounted when shutdown
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: wpa_supplicant
Version: 24
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-23 22:40 UTC by Gerardo Rosales
Modified: 2017-08-08 15:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-08 15:50:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Shutdown log (44.66 KB, text/x-vhdl)
2016-07-23 22:40 UTC, Gerardo Rosales
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1214466 0 unspecified CLOSED Interface is teared down if dbus-daemon exits. wpa_supplicant needs After=dbus.service in unit file. 2021-02-22 00:41:40 UTC

Description Gerardo Rosales 2016-07-23 22:40:34 UTC
Created attachment 1183194 [details]
Shutdown log

Description of problem:

When shutdown the machine if an NFS (three in my case) is mounted the shutdown process takes too much time to unmount the NFS( more than 10 minutes ).

I checked bugzilla and this bug, Bug 1214466, from last year for Fedora 22 seems related to what is happening.

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

Fedora 24 (KDE Spin) with the latest updates

How reproducible:

Mount a NFS partition and shutdown.

Steps to Reproduce:
1. Mount an NFS.
2. Shutdown

Actual results:

The shutdown process is stuck trying to unmount the NFS.

Expected results:

It should unmount NFS automatically and shutdown.

Additional info:

Attached shutdown log file.

dnf info wpa_supplicant --> shows the following:

Installed Packages
Name        : wpa_supplicant
Arch        : x86_64
Epoch       : 1
Version     : 2.5
Release     : 5.fc24
Size        : 3.9 M
Repo        : @System
From repo   : koji-override-0
Summary     : WPA/WPA2/IEEE 802.1X Supplicant
URL         : http://w1.fi/wpa_supplicant/
License     : BSD

Comment 1 Rex Dieter 2016-07-28 23:35:23 UTC
You sure wpa_supplicant is the best component here (why not nfs-utils)?

Comment 2 Fedora End Of Life 2017-07-25 22:00:31 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 3 Fedora End Of Life 2017-08-08 15:50:04 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.