Re: NFS weirdness...
On Thu, 19 Jun 2003, jle wrote: > You are correct, I misread the prev post. mount /home fails. > > # mount /home > mount: /dev/ad0s1h: Device busy > > There are two mount points for /home. One on the local disk (ad0s1h) and > the NFS mount that I mount over /home for shell users, so that HTTTD can > find the public_html dirs. > > The complete fstab on HTTPD: > # DeviceMountpoint FStype Options Dump > Pass# > /dev/ad0s1b noneswapsw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1h /home ufs rw 2 2 > /dev/ad0s1d /tmpufs rw 2 2 > /dev/ad0s1g /usrufs rw 2 2 > /dev/ad0s1e /varufs rw 2 2 > /dev/ad0s1f /var/tmpufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > NFSD:/home2 /home nfs rw,bg 0 0 > > > This worked before I upgraded my webserver (HTTPD) but now it fails to > mount on reboot yet succeeds manually. > > Any Ideas? Multiple mounts for a mountpoint is considered foot-shooting. Either: a) Mount /home off of NFSD:/home2. b) Mount NFSD:/home2 somewhere else. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
> This isn't what I told you to do. This does not access your /etc/fstab > at > all and therefore doesn't accomplish what I was trying to help you > determine. > Do _this_: > mount /home > > With no second parameter, mount will look through /etc/fstab for a > mountpoint > that matches /home and use the config in that line if it finds one. > This > tests your /etc/fstab > I don't believe that 'mount NFSD:/home2 /home' forces mount to access > the > /etc/fstab file. You are correct, I misread the prev post. mount /home fails. # mount /home mount: /dev/ad0s1h: Device busy There are two mount points for /home. One on the local disk (ad0s1h) and the NFS mount that I mount over /home for shell users, so that HTTTD can find the public_html dirs. The complete fstab on HTTPD: # DeviceMountpoint FStype Options Dump Pass# /dev/ad0s1b noneswapsw 0 0 /dev/ad0s1a / ufs rw 1 1 /dev/ad0s1h /home ufs rw 2 2 /dev/ad0s1d /tmpufs rw 2 2 /dev/ad0s1g /usrufs rw 2 2 /dev/ad0s1e /varufs rw 2 2 /dev/ad0s1f /var/tmpufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 NFSD:/home2 /home nfs rw,bg 0 0 This worked before I upgraded my webserver (HTTPD) but now it fails to mount on reboot yet succeeds manually. Any Ideas? TIA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
> As a diagnostic step: > Boot up the system, and then try to manually mount the filesystem with > the command 'mount /usr/src'. If this works ... it pretty much confirms > that your /etc/fstab syntax is correct. If it doesn't work, focus on > /etc/fstab as the problem. > > HTH. > > -- > Bill Moran > Potential Technologies > http://www.potentialtech.com > Thanks Bill, but as I said mounting it manually works fine so I doubt it's fstab. >>> >>>mount NFSD:/home2 /home >>> So that also pretty much clears NFSD too /etc/exports works as evidenced in showmounts -e and that I can manually mount it from HTTPD. I also serve homes via Samba on NFSD, that wouldn't interfere with NFS, would it? Again, since it's buried, here are my exports and fstab. on NFSD: /home2 -maproot=0 -alldirs httpd on HTTPD: NFSD:/home2 /home nfs rw,bg 0 0 Since it mounts manually but not automatically on reboot, I'm still stuck. TIA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
[Please configure your email program so it stops mutilating your emails.] jle wrote: jle said: My new web server won't mount NFS from fstab on reboot. on NFSD: (/etc/exports) /home2 -maproot=0 -alldirs httpd on HTTPD: (/etc/fstab) NFSD:/home2 /home nfs rw,bg 0 0 mount NFSD:/home2 /home Works fine until I reboot. Shouldn't it mount by itself? What am I missing now? Why doesn't HTTPD mount NFSD:/home2 on /home when it reboots? I see no errors in messages on either machine. Both are 5.1-CURRENT. TIA I had the same problem. I found it was due to named starting after the mount was attempted and so it couldn't resolve the name of the nfs server. I changed the fstab to the ip address instead and it worked fine. An example from my fstab: 192.168.1.10:/usr/src /usr/srcnfs rw,soft,intr,nfsv3,tcp 0 0 Give that a go. Regards, Matt. I did try that as my named was starting after "Mounting NFS file systems" too but it still wouldn't mount that line from fstab. It still mounts fine manually but not automatically on reboot like it should. It's probably something like a flag in rc.conf that I'm missing or some other little thing but I'm just not finding it. Thanks for trying. Anyone else with an idea? As a diagnostic step: Boot up the system, and then try to manually mount the filesystem with the command 'mount /usr/src'. If this works ... it pretty much confirms that your /etc/fstab syntax is correct. If it doesn't work, focus on /etc/fstab as the problem. HTH. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
>jle said: >> >> My new web server won't mount NFS from fstab on reboot. >> >> >> on NFSD: (/etc/exports) >> /home2 -maproot=0 -alldirs httpd >> >> on HTTPD: (/etc/fstab) >> NFSD:/home2 /home nfs rw,bg 0 0 >> >> >> mount NFSD:/home2 /home >> >> Works fine until I reboot. Shouldn't it mount by itself? What am I missing >> now? Why doesn't HTTPD mount NFSD:/home2 on /home when it reboots? I see >> no errors in messages on either machine. Both are 5.1-CURRENT. >> >> TIA > >I had the same problem. I found it was due to named starting after the >mount was attempted and so it couldn't resolve the name of the nfs server. >I changed the fstab to the ip address instead and it worked fine. An >example from my fstab: > >192.168.1.10:/usr/src /usr/srcnfs rw,soft,intr,nfsv3,tcp 0 0 > >Give that a go. > >Regards, Matt. I did try that as my named was starting after "Mounting NFS file systems" too but it still wouldn't mount that line from fstab. It still mounts fine manually but not automatically on reboot like it should. It's probably something like a flag in rc.conf that I'm missing or some other little thing but I'm just not finding it. Thanks for trying. Anyone else with an idea? TIA ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
jle said: > > My new web server won't mount NFS from fstab on reboot. > > > on NFSD: (/etc/exports) > /home2 -maproot=0 -alldirs httpd > > on HTTPD: (/etc/fstab) > NFSD:/home2 /home nfs rw,bg 0 0 > > > mount NFSD:/home2 /home > > Works fine until I reboot. Shouldn't it mount by itself? What am I missing > now? Why doesn't HTTPD mount NFSD:/home2 on /home when it reboots? I see > no errors in messages on either machine. Both are 5.1-CURRENT. > > TIA I had the same problem. I found it was due to named starting after the mount was attempted and so it couldn't resolve the name of the nfs server. I changed the fstab to the ip address instead and it worked fine. An example from my fstab: 192.168.1.10:/usr/src /usr/srcnfs rw,soft,intr,nfsv3,tcp 0 0 Give that a go. Regards, Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
