Re: First NFS entry in fstab not mounting at boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 16 May 2010 16:18, BadMagic <badmagic@xxxxxxxxxxxx> wrote:
> On 05/17/2010 12:43 AM, Mike Chambers wrote:
>> On Mon, 2010-05-17 at 00:20 +1000, BadMagic wrote:
>>
>>> On 05/17/2010 12:16 AM, Tim wrote:
>>>
>>>> On Sun, 2010-05-16 at 22:05 +1000, BadMagic wrote:
>>>>
>>>>
>>>>> Basically, whichever entry goes first, doesn't get mounted.
>>>>>
>>>>>
>>>> Are the clients connecting to the network using network manager?
>>>> Perhaps the network isn't up at the time the first mount is attempted,
>>>> but is by the time the next two are.
>>>>
>>>>
>>>>
>>> Possible - if this were the problem, what can be
>>> done to investigate/fix this?
>>>
>> Can you move them further down the fstab list and see what happens?
>> Like put them at the very end or further down than that if already
>> there?
>>
>>
> They're at the bottom already. I've just re-edited fstab - everything's
> ok in there and it's still happening.
>
> The only possibility is as previously suggested, the network isn't up
> for the first entry. Is there some way to tell Network Manager to
> kick-off earlier? Change something in /etc/init.d/NetworkManager or
> something?

Is the "netfs" service running, and is it running after NetworkManager?

On my F12 system, NetworkManager should be first, as it has a priority of 23:

[sam@samlap ~ ]$ grep chkconfig /etc/init.d/netfs
# chkconfig: 345 25 75
[sam@samlap ~ ]$ grep chkconfig /etc/init.d/NetworkManager
# chkconfig: - 23 84

However, inspection of my system reveals that is not the case -
NetworkManager is enabled after netfs:

[sam@samlap ~ ]$ ls /etc/rc5.d/S*netfs
/etc/rc5.d/S25netfs
[sam@samlap ~ ]$ ls /etc/rc5.d/S*NetworkManager
/etc/rc5.d/S27NetworkManager

It appears like somewhere down the line, NetworkManager changed
priority. I can fix that with the services equivalent of "turning off
and on again"

[sam@samlap ~ ]$ sudo chkconfig NetworkManager off
[sudo] password for sam:
[sam@samlap ~ ]$ sudo chkconfig --del NetworkManager
[sam@samlap ~ ]$ sudo chkconfig --add NetworkManager
[sam@samlap ~ ]$ sudo chkconfig NetworkManager on
[sam@samlap ~ ]$ ls /etc/rc5.d/S*NetworkManager
/etc/rc5.d/S23NetworkManager

So, check that your "netfs" service on the clients runs before
NetworkManager - it should, but as my Laptop shows, it may not be.

--
Sam
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux