On Mon, Jul 11, 2005 at 08:46:09PM -0400, Ron Peterson wrote: > On Fri, Jul 08, 2005 at 11:16:19PM +0100, Wackojacko wrote: > > >I have an fstab, which after the usual local disk entries has nfs > > >entries that look like: > > > > > >aservername:/s /s nfs rw,bg,intr,proto=tcp 0 0 > > >aservername:/alum /alum nfs rw,bg,intr,proto=tcp 0 0 > > >aservername:/users /users nfs rw,bg,intr,proto=tcp 0 0 > > >aservername:/u2 /u2 nfs rw,bg,intr,proto=tcp 0 0 > > >etc. > > > > > >On boot, the first mount consistently fails to mount. It manually > > >mounts fine. If I switch entries around, the same thing happens - the > > >first entry fails to mount. > > > > > >Any ideas? > > > > > Is the NFS support compiled into the kernel or loaded as a module. If its > > a module then its possible it isn't loaded in time for the first line in > > fstab, but is loaded by the time the rest are called, or you mount > > manually. I had a similar problem with a Nvidia driver and X which was > > solved by putting the module in /etc/modules so it loads on boot. > > > > Could also try compiling support in the kernel if this doesn't work. > > Thanks. > > I'm using nfs-kernel-server, and I have the relevent nfs kernel stuff > statically linked... :( > > I'm mounting exports from a Tru64 alpha to Debian sarge on a Dell 2800, > BTW. I forgot to try making the first nfs mount a different OS at work > today, and I don't want to reboot from home (Murphy's law...). I'm > going to try that tomorrow and see if that works better.
I have the same problem if the first mount is exported from another Debian box. Whichever mount I put first is not mounted at boot, but will mount fine manually afterwards. ?? -- Ron Peterson Network & Systems Manager Mount Holyoke College http://www.mtholyoke.edu/~rpeterso -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
