Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#12373 - [initscripts] Network filesystems are unmounted after the network itself has been shut down

Attached to Project: Arch Linux
Opened by Olivier (litemotiv) - Sunday, 07 December 2008, 12:03 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 13:59 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Thomas B├Ąchler (brain0)
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

On shutdown, (network) filesystems are unmounted after the network itself has been shut down, this results in a "umount.nfs: DNS resolution failed for xxx.xxx.xxx.xxx: Name or service not known" error thrown by netfs. Changing the order of deamons in rc.conf doesn't solve this.


Additional info:
* package version(s)

20081207-core

* config and/or log files etc.


Steps to reproduce:

1) mount a network filesystem (wireless in my case, don't know if eth0 produces different results)
2) shutdown or reboot, see terminal output
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Saturday, 03 October 2009, 13:59 GMT
Reason for closing:  Fixed
Comment by Thomas (barghest) - Sunday, 07 December 2008, 12:26 GMT
1) mount a network filesystem (wireless in my case, don't know if eth0 produces different results)
2) shutdown or reboot, see terminal output


Confirmed, eth0 produces the same result.
Comment by Glenn Matthys (RedShift) - Sunday, 07 December 2008, 12:42 GMT
Can you show us your DAEMONS rc.conf line?
Comment by Thomas (barghest) - Sunday, 07 December 2008, 12:45 GMT
Sure:

DAEMONS=(syslog-ng network portmap nfslock @netfs @crond @cups hal @cpufreq fam alsa @openntpd @mpd)

The problem also occurs when netfs isn't in the background.
Comment by Olivier (litemotiv) - Sunday, 07 December 2008, 12:47 GMT
Here is mine:

[code]
DAEMONS=(syslog-ng @crond @net-profiles @portmap @nfslock @oss @hal @fuse @cpufreq)
[/code]
Comment by Glenn Matthys (RedShift) - Sunday, 07 December 2008, 12:52 GMT
@litemotiv: netfs isn't even in your DAEMONS line?
Comment by Olivier (litemotiv) - Sunday, 07 December 2008, 13:02 GMT
@Glenn: i don't automount my network shares on boot, so netfs is not yet needed then. shutdown does invoke /rc.d/netfs though to unmount the network shares.
Comment by Glenn Matthys (RedShift) - Sunday, 07 December 2008, 13:05 GMT
@Aaron: this could be solved by reversing the order in rc.shutdown. First process all the daemons in /var/run/daemons that are NOT in rc.conf, then all those in rc.conf. Right now rc.shutdown first processes DAEMONS and then any leftovers in /var/run/daemons.
Comment by Gavin Bisesi (Daenyth) - Monday, 08 December 2008, 01:07 GMT
I like RedShift's solution. I actually thought that was the default way it was handled.. Apparantly not..
Comment by Aaron Griffin (phrakture) - Monday, 08 December 2008, 22:11 GMT
It's a little technically hard to reverse those two, as bash doesn't give us a clean "is x in array" capability. It's doable, but messy.

I agree with this though, that "leftovers" should be stopped first... anyone want to code it up? is we add a "in_array" function (with support for ignoring ! and @ prefixes), this should be much easier.

Additional point: If we remove the rc.shutdown check for the ! prefix, and just use the /var/run/daemons dir, we could do the exact same thing by adding it to the daemons array with !netfs. Shutdown will stop it in the right order if it is running.
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 15 June 2009, 23:43 GMT
what is the status of this issue with latest initscripts?
Comment by Olivier (litemotiv) - Saturday, 27 June 2009, 19:57 GMT
i can confirm this bug still exists with the current scripts
Comment by Aaron Griffin (phrakture) - Thursday, 30 July 2009, 16:51 GMT Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 30 July 2009, 18:05 GMT
@Aaron: In case of this help, must also fix and change the order in rc.single

Patch for it attached.
Comment by Aaron Griffin (phrakture) - Thursday, 30 July 2009, 18:19 GMT
Thanks, patch applied and pushed

Loading...