Re: mounting nfs on boot -- Was: Replacing systemd
On Tue, Mar 04, 2014 at 01:52:19PM +, Darac Marjal wrote: Boot speed isn't systemd's goal. It's just a side-effect. Systemd's real goals are being event driven (so, for example, you don't mount a file system until the device is ready - at the moment, debian does this with a two-pass mount script: one pass to mount local filesystems, then another after networking is up to mount remote filesystems, but this gets messy if you have a complex system.) and snip Hey, maybe you can tell me why my nfs mounts don't get mounted at boot time on my computer that uses wicd to manage its wireless network interface. The network comes up at boot time (it doesn't require a user to log in first). Currently I stick sleep 10s mount -a in /etc/rc.local in order to mount the nfs shares, but I know that shouldn't be necessary. -Rob signature.asc Description: Digital signature
Re: mounting nfs on boot -- Was: Replacing systemd
On 05/03/14 10:36, Rob Owens wrote: On Tue, Mar 04, 2014 at 01:52:19PM +, Darac Marjal wrote: Boot speed isn't systemd's goal. It's just a side-effect. Systemd's real goals are being event driven (so, for example, you don't mount a file system until the device is ready - at the moment, debian does this with a two-pass mount script: one pass to mount local filesystems, then another after networking is up to mount remote filesystems, but this gets messy if you have a complex system.) and snip Hey, maybe you can tell me why my nfs mounts don't get mounted at boot time on my computer that uses wicd to manage its wireless network interface. The network comes up at boot time (it doesn't require a user to log in first). Currently I stick sleep 10s mount -a in /etc/rc.local in order to mount the nfs shares, but I know that shouldn't be necessary. -Rob Where are those nfs shares mounted (path)? Kind regards -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/53166aa4.8030...@gmail.com
Re: mounting nfs on boot -- Was: Replacing systemd
On Wed, Mar 05, 2014 at 11:07:00AM +1100, Scott Ferguson wrote: On 05/03/14 10:36, Rob Owens wrote: On Tue, Mar 04, 2014 at 01:52:19PM +, Darac Marjal wrote: Boot speed isn't systemd's goal. It's just a side-effect. Systemd's real goals are being event driven (so, for example, you don't mount a file system until the device is ready - at the moment, debian does this with a two-pass mount script: one pass to mount local filesystems, then another after networking is up to mount remote filesystems, but this gets messy if you have a complex system.) and snip Hey, maybe you can tell me why my nfs mounts don't get mounted at boot time on my computer that uses wicd to manage its wireless network interface. The network comes up at boot time (it doesn't require a user to log in first). Currently I stick sleep 10s mount -a in /etc/rc.local in order to mount the nfs shares, but I know that shouldn't be necessary. -Rob Where are those nfs shares mounted (path)? /mnt/music /mnt/pics_and_clips and so-on. signature.asc Description: Digital signature
Re: mounting nfs on boot -- Was: Replacing systemd
On 05/03/14 11:34, Rob Owens wrote:
On Wed, Mar 05, 2014 at 11:07:00AM +1100, Scott Ferguson wrote:
On 05/03/14 10:36, Rob Owens wrote:
On Tue, Mar 04, 2014 at 01:52:19PM +, Darac Marjal wrote:
Boot speed isn't systemd's goal. It's just a side-effect.
Systemd's real goals are being event driven (so, for example,
you don't mount a file system until the device is ready - at
the moment, debian does this with a two-pass mount script:
one pass to mount local filesystems, then another after
networking is up to mount remote filesystems, but this gets
messy if you have a complex system.) and
snip
Hey, maybe you can tell me why my nfs mounts don't get mounted
at boot time on my computer that uses wicd to manage its
wireless network interface. The network comes up at boot time
(it doesn't require a user to log in first). Currently I stick
sleep 10s mount -a in /etc/rc.local in order to mount the
nfs shares, but I know that shouldn't be necessary.
-Rob
Where are those nfs shares mounted (path)?
/mnt/music /mnt/pics_and_clips
and so-on.
Thanks.
I've used the /etc/rc.local mount -a workaround in the past,
without the need for the sleep command.
In my cases I had the nfs mount being called from fstab, using the
nfsvers=3 option helped when the server was Version 3 (vers= is a
more portable version of that option). You can also
use the timeo=n to set a wait period instead of sleep in
/etc/rc.local e.g. timeo=100 (time is in deciseconds). Use it in
combination with the bg flag and the appropriate retry value. See man
nfs for more a useful and accurate explanation.
NOTE: I'm assuming you mean that your nfs server/s is accessed with
wireless.
I'm also assuming you've checked the logs for clues. If so you may be
able to get more information by adding the -v (for verbose) to the
mount call in /etc/network/ifup.d/mountnfs (WARNING - untested, thanks
for testing)
e.g.:-
# cp /etc/network/ifup.d/mountnfs{,.bak}
then edit /etc/network/ifup.d/mountnfs
and change:-
if [ $NETFS ]
then
mount -a -t$NETFS
fi
to:-
if [ $NETFS ]
then
mount -va -t$NETFS
fi
and reboot (or restart network services, after umounting the nfs
shares - don't forget to comment out your line in /etc/rc.local)
Kind regards
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/531686f8@gmail.com
more on ( mount NFS during boot problem )
Even more wierd, I've reinstalled kernel-image (2.0.35 right from slink) the NFS started working, but dhcpcd stopped - just gives me IP 0.0.0.0 Reinstallation of dhcpcd did not help. Any ideas ? Sergey. On Fri, 23 Oct 1998, Sergey V Kovalyov wrote: Hi, I have a wierd problem: during boot process mount fails with the following message: Starting portmapper... Mounting remote filesystems... mount: RPC: Program not registered But after the boot mount -a works perfectly. This runs latest slink from unstable. I did not have such a problem on a similar machine a month before. Any idea of what might cause the problem and how to work around it ? Something, I think, relevant: later in the process netbase starts its own portmapper. Sergey.
Re: mount NFS during boot problem
On Fri, 23 Oct 1998, Sergey V Kovalyov wrote: Hi, I have a wierd problem: during boot process mount fails with the following message: Starting portmapper... Mounting remote filesystems... mount: RPC: Program not registered I saw this once when rpc.mountd and/or rpc.nfsd on the server machine was not up (i.e. on the other computer). So, maybe it is really the missing local portmapper. Find out where it gets started, and take a look at the logs of the other computer, if your machine tries to connect or not. Gruss -- Lukas Eppler (godot) http://www.fear.ch telnet://soil.fear.ch: talk:[EMAIL PROTECTED]
mount NFS during boot problem
Hi, I have a wierd problem: during boot process mount fails with the following message: Starting portmapper... Mounting remote filesystems... mount: RPC: Program not registered But after the boot mount -a works perfectly. This runs latest slink from unstable. I did not have such a problem on a similar machine a month before. Any idea of what might cause the problem and how to work around it ? Something, I think, relevant: later in the process netbase starts its own portmapper. Sergey.
No nfs, no boot
Hi, I have my machine setup to mount a disk on another (Debian) linux machine. Unfortunately when I was rebooting my system, the other machine didn't want to serve me, so my machine hung with: NFS server ottifant not responding, still trying. Now the obvious solution is to fix up the other machine, but the thing which worried me most was the fact that the attempt to nfs mount didn't timeout. Which means that my system is entirely dependent on the other system in order to boot. Why is this so? Thanks. - Mark Phillips [EMAIL PROTECTED] They told me I was gullible ... and I believed them! -
Re: No nfs, no boot
I have my machine setup to mount a disk on another (Debian) linux machine. Unfortunately when I was rebooting my system, the other machine didn't want to serve me, so my machine hung with: NFS server ottifant not responding, still trying. Now the obvious solution is to fix up the other machine, but the thing which worried me most was the fact that the attempt to nfs mount didn't timeout. Which means that my system is entirely dependent on the other system in order to boot. Why is this so? I am guessing that something is probably trying to access a file on the NFS mounted drive. You could try using the soft option when mounting it. From the nfs man page: soft If an NFS file operation has a major time out then report an I/O error to the calling program. The default is to continue retry ing NFS file operations indefinitely. Alternatively, use amd to automount the drive as necessary. That works really nicely. Steve
Re: No nfs, no boot
On Mon, 7 Apr 1997, Steve Hsieh wrote: Now the obvious solution is to fix up the other machine, but the thing which worried me most was the fact that the attempt to nfs mount didn't timeout. Which means that my system is entirely dependent on the other system in order to boot. I am guessing that something is probably trying to access a file on the NFS mounted drive. You could try using the soft option when mounting it. From the nfs man page: soft If an NFS file operation has a major time- out then report an I/O error to the calling program. The default is to continue retry- ing NFS file operations indefinitely. Also from nfs(5): bg If the first NFS mount attempt times out, continue trying the mount in the back ground. The default is to not to back ground the mount on timeout but fail. This is almost necessary if two NFS servers are clients of each other. Pete -- Peter J. Templin, Jr. Client Services Analyst Computer Communication Services tel: (717) 524-1590 Bucknell University [EMAIL PROTECTED]
