Hi,
> Inside of /etc/rc.d/init.d/netfs - the part that mounts the NFS shares, I
> put:
>
> sleep 30
Is your switch a Cisco one?
http://fedoraproject.org/wiki/Anaconda/NetworkIssues#Cisco_Switch_Issues
Regards,
Fernando.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or c
Original Message
Subject:Re: First NFS entry in fstab not mounting at boot
Date: Tue, 18 May 2010 02:49:35 +1000
From: BadMagic
To: Community support for Fedora users
On 05/17/2010 08:33 PM, Karl-Olov Serrander wrote:
> On Mon, 17 May 2010, Wolfgan
Karl-Olov Serrander writes:
> On Mon, 17 May 2010, Wolfgang S. Rupprecht wrote:
>> echo "NETWORKWAIT=yes" >> /etc/sysconfig/network
> Is this documented somewhere ?
>
> It is not in /usr/share/doc/initscripts-9.02.1/sysconfig.txt for Fedora 12
> or /usr/share/doc/initscripts-9.12/sysconfig.txt fo
On 05/17/2010 08:33 PM, Karl-Olov Serrander wrote:
> On Mon, 17 May 2010, Wolfgang S. Rupprecht wrote:
>
>> BadMagic writes:
>>
>>> On 05/17/2010 12:16 AM, Tim wrote:
>>>
On Sun, 2010-05-16 at 22:05 +1000, BadMagic wrote:
> Basically, whichever entry goes
On Mon, 17 May 2010, Wolfgang S. Rupprecht wrote:
> BadMagic writes:
>> 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?
>>
On Mon, 2010-05-17 at 00:46 -0700, Wolfgang S. Rupprecht wrote:
> echo "NETWORKWAIT=yes" >> /etc/sysconfig/network
>
> reboot
>
> I'm not sure why networkwait isn't the default. Running without it
> causes quite a bit of the stuff that relies on the network to fail.
Yes, all the fun of watch
On Mon, 2010-05-17 at 02:08 -0400, Chris Kloiber wrote:
> In this case you might even want to add _netdev.
>
> _netdev
> The filesystem resides on a device that requires network access
> (used to prevent the system from attempting to mount these
> filesystems until the net
BadMagic writes:
> 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 mou
Although I am not familiar with nfsv4, for nfsv3 'defaults' could be a
pretty major performance problem.
I typically use rw,hard,intr,rsize=8192,wsize=8192,
In this case you might even want to add _netdev.
_netdev
The filesystem resides on a device that requires network access
(u
BadMagic wrote:
> Basically, whichever entry goes first, doesn't get mounted.
> I can manually mount it after I've logged in like:
> If I repeat the top entry like:
are the drives are spun down and at rest when you first try to mount?
'man nfs' for timeout setting info in fstab.
are you co
Have you tried the bg mount option?
It should background any mount that fails and retry periodically.
man nfs
--
birger
Typed on my cellphone so any non-conformity with regard to posting rules can be
blamed on my mailer
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or ch
The chkconfig line within the rc script only specifies the default priorities.
Turning the service off and on again will correctly change the actual priority
to the current default. Chkconfig also has a resetpriorities option that does
the same ting. I would not change the script. If you want to
On 05/16/2010 11:14 AM, Sam Sharpe wrote:
> On 16 May 2010 16:33, Sam Sharpe wrote:
>> So, check that your "netfs" service on the clients runs before
>> NetworkManager - it should, but as my Laptop shows, it may not be.
>
> typo - netfs should run *after* NetworkManager
netfs _does_ start after N
On Sun, 16 May 2010 19:32:15 +0100
Sam Sharpe wrote:
> but there is usually a reason why something is a
> particular priority and hence changing it is not necessarily a good
> idea.
I once examined my system when trying to figure out how to
write an init script and found virtually none of the scr
On 16 May 2010 18:37, Genes MailLists wrote:
> On 05/16/2010 12:18 PM, BadMagic wrote:
>>
>> True - I'll try it.
>>
>> I tried changing the order as Sam suggested:
>>
>> [...@samlap ~ ]$ sudo chkconfig --del NetworkManager
>> [...@samlap ~ ]$ sudo chkconfig --add NetworkManager
>> [...@samlap ~ ]$
On 05/16/2010 12:18 PM, BadMagic wrote:
>
> True - I'll try it.
>
> I tried changing the order as Sam suggested:
>
> [...@samlap ~ ]$ sudo chkconfig --del NetworkManager
> [...@samlap ~ ]$ sudo chkconfig --add NetworkManager
> [...@samlap ~ ]$ sudo chkconfig NetworkManager on
> [...@samlap ~
On 05/17/2010 02:01 AM, Genes MailLists wrote:
> On 05/16/2010 10:38 AM, BadMagic wrote:
>
>>> One solution is to use autofs ... it will mount on demand and
>>> therefore that problem -should- just go away (if thats the problem)
>>>
>>> gene/
>>>
>>>
>> That may work but I'd rather
On 16 May 2010 16:33, Sam Sharpe wrote:
> So, check that your "netfs" service on the clients runs before
> NetworkManager - it should, but as my Laptop shows, it may not be.
typo - netfs should run *after* NetworkManager
FWIW, If I'm right about the cause, then switching to "network" rather
than
On 05/16/2010 10:38 AM, BadMagic wrote:
>>One solution is to use autofs ... it will mount on demand and
>> therefore that problem -should- just go away (if thats the problem)
>>
>> gene/
>>
>
> That may work but I'd rather find out why it isn't working when it
> should be.
>
>
This i
On 16 May 2010 16:18, BadMagic 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, do
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.
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?
> >
On 05/17/2010 12:37 AM, Sam Sharpe wrote:
> On 16 May 2010 13:05, BadMagic wrote:
>
>
>> In my /etc/fstab, I've got 3 NFS entries:
>>
>> fs1:/data/unix /unixnfs defaults0 0
>> fs1:/data/windows /windows nfs defaults0 0
>> fs2:/storage1 /backup nfs
On 05/17/2010 12:22 AM, Genes MailLists wrote:
> On 05/16/2010 10:20 AM, 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.
>
On 16 May 2010 13:05, BadMagic wrote:
> In my /etc/fstab, I've got 3 NFS entries:
>
> fs1:/data/unix /unix nfs defaults 0 0
> fs1:/data/windows /windows nfs defaults 0 0
> fs2:/storage1 /backup nfs defaults 0 0
>
> In this order, 'fs1:/data/unix' wo
On 05/16/2010 10:20 AM, 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 netw
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 atte
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.
--
[...@lo
On 05/16/2010 10:28 PM, Tom Horsley wrote:
> On Sun, 16 May 2010 22:05:09 +1000
> BadMagic wrote:
>
>
>> Does anyone know what's going on?
>>
> I don't know what is going on, but I had a problem where
> the first DNS lookup I'd ever do would almost always fail
> (I'm running named as a lo
Tom Horsley wrote:
> On Sun, 16 May 2010 22:05:09 +1000
> BadMagic wrote:
>
>> Does anyone know what's going on?
>
> I don't know what is going on, but I had a problem where
> the first DNS lookup I'd ever do would almost always fail
> (I'm running named as a local DNS server).
So Badmagic shoul
On Sun, 16 May 2010 22:05:09 +1000
BadMagic wrote:
> Does anyone know what's going on?
I don't know what is going on, but I had a problem where
the first DNS lookup I'd ever do would almost always fail
(I'm running named as a local DNS server). I made a silly
little "system service" script to sta
Hi,
Im running Fedora Core 12 x86_64 on my computer.
# uname -a
Linux apollo.foo-unix.ARPA 2.6.32.11-99.fc12.x86_64 #1 SMP Mon Apr 5
19:59:38 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux
I have 2 NFS servers in my garage:
fs1 - an x86 box running FreeBSD 8.0-RELEASE
fs2 - a Sun E450 running Solaris
32 matches
Mail list logo
