Re: NFS Problems/Questions
On Sat, Jun 30, 2007 at 07:33:19PM -0400, Jason Morgan wrote: On Sat, Jun 23, 2007 at 07:42:24PM -0400, Jason Morgan wrote: On Sat, Jun 23, 2007 at 12:46:27PM -0700, Michael Smith wrote: Hello Jason: On Jun 23, 2007, at 9:34 AM, Jason Morgan wrote: I've been having some trouble with NFS performance for some time and now that class is out, I've had a bit of time to investigate but I'm stuck. Below are the details of my investigation. Hopefully, someone here can give me some advice. The basic problem is that my NFS performance is very slow. Right now, I am connecting two workstations to a NFS server, which has my home directory, etc, mounted. They are connected over a gigabit network (right now with mtu set to 7000, which is supported by all hardware -- changing it to 1500 has no effect on performance, which is strange). Each system is running 6.2-RELEASE or -STABLE. Each system is also using the following network card: # ifconfig sk0 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 7000 options=bRXCSUM,TXCSUM,VLAN_MTU inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 ether 00:17:9a:bb:05:87 media: Ethernet autoselect (1000baseTX full- duplex,flag0,flag1) status: active # dmesg | grep sk skc0: D-Link DGE-530T Gigabit Ethernet port 0xec00-0xecff mem 0xfdff8000-0xfdffbfff irq 18 at device 10.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:17:9a:XX:XX:XX ## Server /etc/rc.conf settings rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 12 nfs_bufpackets=32 mountd_flags=-r ## Client /etc/rc.conf settings nfs_client_enable=YES nfs_bufpackets=32 nfsiod_enable=YES nfsiod_flags=-n 6 rpc_lockd_enable=YES rpc_statd_enable=YES rpcbind_enable=YES ## /etc/exports /usr -alldirs,maproot=root client1 client2 For performance benchmarking, I am using dd. Locally from the server, this is a representative result when writing a 1GB file: ## Local write test (for an upper-bound on what to expect). # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 19.580184 secs (53552919 bytes/sec) Connecting from a client (both clients get approximately the same results). ## Remote connection (UDP), mounted in /etc/fstab as with flags: ## rw,-U,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 101.151139 secs (10366428 bytes/sec) ## Remote connection (TCP), mounted in /etc/fstab as with flags: ## rw,-T,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 59.668585 secs (17573334 bytes/sec) As can be seen above, TCP is much faster than UPD. I have tried many different mount settings and these are the best results I could get. To test whether or not I have having network issues, I transferred the same nfs.dat file via a http connection and got ~32MB/sec -- almost 2x the speed of the TCP NFS connection. 32MB/sec is about what I would expect given that my fastest write speed is ~50MB/sec. At this point I am stumped. I have tried increasing/changing the number of nfsiod servers as well as nfs_bufpackets. No matter what settings I change, the results are always the same. I get only two errors, first on /var/log/messages on the server I have just begun seeing: Jun 22 21:13:47 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:47 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted This appeared after I added a route; however, I added the route after many of the tests were done. I get the same results now as before the new route. On one of the clients (the one running 6.2-RELEASE-p1), I also get a nasty error: nfs/tcp clnt: Error 60 reading socket, tearing down TCP connection This cropped up last night after I tweaked some settings. They have now been changed back, but I still get this error. The other client is unaffected. I appreciate any help people can provide on tracking down the issues. Sorry about the long email -- just trying to be thorough. Of course, I've searched the Internet and can't find any clear assistence on these issues. Cheers, ~Jason We use the
Re: NFS Problems/Questions
On Sat, Jun 23, 2007 at 07:42:24PM -0400, Jason Morgan wrote: On Sat, Jun 23, 2007 at 12:46:27PM -0700, Michael Smith wrote: Hello Jason: On Jun 23, 2007, at 9:34 AM, Jason Morgan wrote: I've been having some trouble with NFS performance for some time and now that class is out, I've had a bit of time to investigate but I'm stuck. Below are the details of my investigation. Hopefully, someone here can give me some advice. The basic problem is that my NFS performance is very slow. Right now, I am connecting two workstations to a NFS server, which has my home directory, etc, mounted. They are connected over a gigabit network (right now with mtu set to 7000, which is supported by all hardware -- changing it to 1500 has no effect on performance, which is strange). Each system is running 6.2-RELEASE or -STABLE. Each system is also using the following network card: # ifconfig sk0 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 7000 options=bRXCSUM,TXCSUM,VLAN_MTU inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 ether 00:17:9a:bb:05:87 media: Ethernet autoselect (1000baseTX full- duplex,flag0,flag1) status: active # dmesg | grep sk skc0: D-Link DGE-530T Gigabit Ethernet port 0xec00-0xecff mem 0xfdff8000-0xfdffbfff irq 18 at device 10.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:17:9a:XX:XX:XX ## Server /etc/rc.conf settings rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 12 nfs_bufpackets=32 mountd_flags=-r ## Client /etc/rc.conf settings nfs_client_enable=YES nfs_bufpackets=32 nfsiod_enable=YES nfsiod_flags=-n 6 rpc_lockd_enable=YES rpc_statd_enable=YES rpcbind_enable=YES ## /etc/exports /usr -alldirs,maproot=root client1 client2 For performance benchmarking, I am using dd. Locally from the server, this is a representative result when writing a 1GB file: ## Local write test (for an upper-bound on what to expect). # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 19.580184 secs (53552919 bytes/sec) Connecting from a client (both clients get approximately the same results). ## Remote connection (UDP), mounted in /etc/fstab as with flags: ## rw,-U,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 101.151139 secs (10366428 bytes/sec) ## Remote connection (TCP), mounted in /etc/fstab as with flags: ## rw,-T,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 59.668585 secs (17573334 bytes/sec) As can be seen above, TCP is much faster than UPD. I have tried many different mount settings and these are the best results I could get. To test whether or not I have having network issues, I transferred the same nfs.dat file via a http connection and got ~32MB/sec -- almost 2x the speed of the TCP NFS connection. 32MB/sec is about what I would expect given that my fastest write speed is ~50MB/sec. At this point I am stumped. I have tried increasing/changing the number of nfsiod servers as well as nfs_bufpackets. No matter what settings I change, the results are always the same. I get only two errors, first on /var/log/messages on the server I have just begun seeing: Jun 22 21:13:47 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:47 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted This appeared after I added a route; however, I added the route after many of the tests were done. I get the same results now as before the new route. On one of the clients (the one running 6.2-RELEASE-p1), I also get a nasty error: nfs/tcp clnt: Error 60 reading socket, tearing down TCP connection This cropped up last night after I tweaked some settings. They have now been changed back, but I still get this error. The other client is unaffected. I appreciate any help people can provide on tracking down the issues. Sorry about the long email -- just trying to be thorough. Of course, I've searched the Internet and can't find any clear assistence on these issues. Cheers, ~Jason We use the following settings on a mail cluster that's pushing about 50 MB/sec sustained. 10.211.1.213:/m0/mail/m0nfs rw,tcp,intr,noatime,nfsv3,-w=65536,-r=65536 # NFS
Re: NFS Problems/Questions
Hello Jason: On Jun 23, 2007, at 9:34 AM, Jason Morgan wrote: I've been having some trouble with NFS performance for some time and now that class is out, I've had a bit of time to investigate but I'm stuck. Below are the details of my investigation. Hopefully, someone here can give me some advice. The basic problem is that my NFS performance is very slow. Right now, I am connecting two workstations to a NFS server, which has my home directory, etc, mounted. They are connected over a gigabit network (right now with mtu set to 7000, which is supported by all hardware -- changing it to 1500 has no effect on performance, which is strange). Each system is running 6.2-RELEASE or -STABLE. Each system is also using the following network card: # ifconfig sk0 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 7000 options=bRXCSUM,TXCSUM,VLAN_MTU inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 ether 00:17:9a:bb:05:87 media: Ethernet autoselect (1000baseTX full- duplex,flag0,flag1) status: active # dmesg | grep sk skc0: D-Link DGE-530T Gigabit Ethernet port 0xec00-0xecff mem 0xfdff8000-0xfdffbfff irq 18 at device 10.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:17:9a:XX:XX:XX ## Server /etc/rc.conf settings rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 12 nfs_bufpackets=32 mountd_flags=-r ## Client /etc/rc.conf settings nfs_client_enable=YES nfs_bufpackets=32 nfsiod_enable=YES nfsiod_flags=-n 6 rpc_lockd_enable=YES rpc_statd_enable=YES rpcbind_enable=YES ## /etc/exports /usr -alldirs,maproot=root client1 client2 For performance benchmarking, I am using dd. Locally from the server, this is a representative result when writing a 1GB file: ## Local write test (for an upper-bound on what to expect). # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 19.580184 secs (53552919 bytes/sec) Connecting from a client (both clients get approximately the same results). ## Remote connection (UDP), mounted in /etc/fstab as with flags: ## rw,-U,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 101.151139 secs (10366428 bytes/sec) ## Remote connection (TCP), mounted in /etc/fstab as with flags: ## rw,-T,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 59.668585 secs (17573334 bytes/sec) As can be seen above, TCP is much faster than UPD. I have tried many different mount settings and these are the best results I could get. To test whether or not I have having network issues, I transferred the same nfs.dat file via a http connection and got ~32MB/sec -- almost 2x the speed of the TCP NFS connection. 32MB/sec is about what I would expect given that my fastest write speed is ~50MB/sec. At this point I am stumped. I have tried increasing/changing the number of nfsiod servers as well as nfs_bufpackets. No matter what settings I change, the results are always the same. I get only two errors, first on /var/log/messages on the server I have just begun seeing: Jun 22 21:13:47 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:47 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted This appeared after I added a route; however, I added the route after many of the tests were done. I get the same results now as before the new route. On one of the clients (the one running 6.2-RELEASE-p1), I also get a nasty error: nfs/tcp clnt: Error 60 reading socket, tearing down TCP connection This cropped up last night after I tweaked some settings. They have now been changed back, but I still get this error. The other client is unaffected. I appreciate any help people can provide on tracking down the issues. Sorry about the long email -- just trying to be thorough. Of course, I've searched the Internet and can't find any clear assistence on these issues. Cheers, ~Jason We use the following settings on a mail cluster that's pushing about 50 MB/sec sustained. 10.211.1.213:/m0/mail/m0nfs rw,tcp,intr,noatime,nfsv3,-w=65536,-r=65536 # NFS Server rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 16 -h 10.211.1.213 mountd_flags=-r I would imagine the larger read/write values above would be fine for you as well, given you have Gigabit links. The 'noatime' setting may be problematic depending on your application. You might want to Google specifics on what
Re: NFS Problems/Questions
On Sat, Jun 23, 2007 at 12:46:27PM -0700, Michael Smith wrote: Hello Jason: On Jun 23, 2007, at 9:34 AM, Jason Morgan wrote: I've been having some trouble with NFS performance for some time and now that class is out, I've had a bit of time to investigate but I'm stuck. Below are the details of my investigation. Hopefully, someone here can give me some advice. The basic problem is that my NFS performance is very slow. Right now, I am connecting two workstations to a NFS server, which has my home directory, etc, mounted. They are connected over a gigabit network (right now with mtu set to 7000, which is supported by all hardware -- changing it to 1500 has no effect on performance, which is strange). Each system is running 6.2-RELEASE or -STABLE. Each system is also using the following network card: # ifconfig sk0 sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 7000 options=bRXCSUM,TXCSUM,VLAN_MTU inet 10.0.0.2 netmask 0xff00 broadcast 10.0.0.255 ether 00:17:9a:bb:05:87 media: Ethernet autoselect (1000baseTX full- duplex,flag0,flag1) status: active # dmesg | grep sk skc0: D-Link DGE-530T Gigabit Ethernet port 0xec00-0xecff mem 0xfdff8000-0xfdffbfff irq 18 at device 10.0 on pci0 skc0: DGE-530T Gigabit Ethernet Adapter rev. (0x9) sk0: Marvell Semiconductor, Inc. Yukon on skc0 sk0: Ethernet address: 00:17:9a:XX:XX:XX ## Server /etc/rc.conf settings rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 12 nfs_bufpackets=32 mountd_flags=-r ## Client /etc/rc.conf settings nfs_client_enable=YES nfs_bufpackets=32 nfsiod_enable=YES nfsiod_flags=-n 6 rpc_lockd_enable=YES rpc_statd_enable=YES rpcbind_enable=YES ## /etc/exports /usr -alldirs,maproot=root client1 client2 For performance benchmarking, I am using dd. Locally from the server, this is a representative result when writing a 1GB file: ## Local write test (for an upper-bound on what to expect). # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 19.580184 secs (53552919 bytes/sec) Connecting from a client (both clients get approximately the same results). ## Remote connection (UDP), mounted in /etc/fstab as with flags: ## rw,-U,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 101.151139 secs (10366428 bytes/sec) ## Remote connection (TCP), mounted in /etc/fstab as with flags: ## rw,-T,-3,-r=32768,-w=32768 # dd if=/dev/zero of=./nfs.dat bs=1024k count=1000 1000+0 records in 1000+0 records out 1048576000 bytes transferred in 59.668585 secs (17573334 bytes/sec) As can be seen above, TCP is much faster than UPD. I have tried many different mount settings and these are the best results I could get. To test whether or not I have having network issues, I transferred the same nfs.dat file via a http connection and got ~32MB/sec -- almost 2x the speed of the TCP NFS connection. 32MB/sec is about what I would expect given that my fastest write speed is ~50MB/sec. At this point I am stumped. I have tried increasing/changing the number of nfsiod servers as well as nfs_bufpackets. No matter what settings I change, the results are always the same. I get only two errors, first on /var/log/messages on the server I have just begun seeing: Jun 22 21:13:47 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:47 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(dc1, 224.0.0.2): Operation not permitted Jun 22 21:13:50 crichton routed[666]: sendto(sk0, 224.0.0.2): Operation not permitted This appeared after I added a route; however, I added the route after many of the tests were done. I get the same results now as before the new route. On one of the clients (the one running 6.2-RELEASE-p1), I also get a nasty error: nfs/tcp clnt: Error 60 reading socket, tearing down TCP connection This cropped up last night after I tweaked some settings. They have now been changed back, but I still get this error. The other client is unaffected. I appreciate any help people can provide on tracking down the issues. Sorry about the long email -- just trying to be thorough. Of course, I've searched the Internet and can't find any clear assistence on these issues. Cheers, ~Jason We use the following settings on a mail cluster that's pushing about 50 MB/sec sustained. 10.211.1.213:/m0/mail/m0nfs rw,tcp,intr,noatime,nfsv3,-w=65536,-r=65536 # NFS Server rpcbind_enable=YES rpc_lockd_enable=YES rpc_statd_enable=YES nfs_server_enable=YES nfs_server_flags=-u -t -n 16 -h 10.211.1.213 mountd_flags=-r I would imagine the larger read/write
Re: NFS problems!
Anders Troback [EMAIL PROTECTED] writes: Hi, I'm having some problems with NFS lately! NFS server FreeBSD 6.1-RELESE NFS client FreeBSD 6.2-PRERELASE (STABLE) I'm using NFS to serve /home via amd but sometimes programs hangs and not even kill -9 will work. I have to restart rpc.lockd, rpc.statd and nfsd to get rid of the programs! If one program hangs many will follow and some will not start. Programs like Citrix Client Manager (wfcmgr), konqueror, konsole and gftp are all examples on programs that don't start. Sins 6.2-PRERELEASE sometimes wfcmgr don't start even if there are no programs hanging! You're lucky. I can't even get X to load and the whole vfs won't shut down cleanly once I've tried. I have yet to try other FreeBSD releases though. Matthew -- I must take issue with the term a mere child, for it has been my invariable experience that the company of a mere child is infinitely preferable to that of a mere adult. -- Fran Lebowitz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS problems!
Anders Troback [EMAIL PROTECTED] writes: I'm having some problems with NFS lately! NFS server FreeBSD 6.1-RELESE NFS client FreeBSD 6.2-PRERELASE (STABLE) I'm using NFS to serve /home via amd but sometimes programs hangs and not even kill -9 will work. I have to restart rpc.lockd, rpc.statd and nfsd to get rid of the programs! If one program hangs many will follow and some will not start. Programs like Citrix Client Manager (wfcmgr), konqueror, konsole and gftp are all examples on programs that don't start. Sins 6.2-PRERELEASE sometimes wfcmgr don't start even if there are no programs hanging! This problem first occurred in 6.1-STABLE but disappear in 6.1-RELEASE and since 6.1-RELEASE-p4 (not 100% sure if it was p4 or p5) it's back! Does anyone have any idea what's going on here? There have been some discussions of locking problems; see the -net list. In this case, though, I would tend to go with a soft mount anyway, which might reduce the symptoms considerably. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS problems
Karel Miklav wrote: I have a FreeBSD 5.3RC1 and Mandrake 10 Connected over NFS. Server is on Mandrake and FreeBSD is only client. Transfer rate for files is great, but scanning folders on the NFS mount is ubearably slow. CPU usage on both machines is close to 0%, on Mandrake I can see a nfsd daemon or two fired up from time to time, client is waiting in the loop. Might it be that you are having issues with different MTU size? -- Jakob Breivik Grimstveit, http://www.grimstveit.no/jakob, +47 48298152 Bruk Newsergalleriet! No på http://www.newsergalleriet.no/ Treng du noko på CD?: http://www.grimstveit.no/jakob/burncd_no ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Problems...
There shouldn't BE a /home2 on HTTPD but I figured out what happened. I copied /etc/group /etc/passwd /etc/pwd.db and /etc/master.passwd from NFSD to HTTPD to sync users and passwords and forgot to edit the home dir with vipw. I just did a global search and replace of /home2 to /home and rebuilt the pwd.db and it mounted fine and apache now serves public_html from the users shells. However, on reboot it doesn't mount from /etc/fstab, I have to mount it manually for some reason. So now I'm down to the one NFS problem. on NFSD: (/etc/exports) /home2 -maproot=0 -alldirs httpd on HTTPD: (/etc/fstab) NFSD:/home2 /home nfs rw,bg 0 0 manually mounting works mount NFSD:/home2 /home Works fine until I reboot. Shouldn't it mount by itself like it used to? What am I missing now? Why doesn't HTTPD mount NFSD:/home2 on /home when it reboots? TIA Hi, In your fstab, what is the bg purpose ? I never seen this option before. Make sure such option is usable. Pote ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Problems...
On Thu, Jun 05, 2003 at 01:03:17AM +0200 or thereabouts, Bernd Walter seemed to write: On Wed, Jun 04, 2003 at 02:21:29PM -0700, jle wrote: I retired my old p200 fbsd 4.4-stable web server and built a newer box for it. I used to mount the /home2 dir from my nfs server (fbsd 5.1-current) to /home on the webserver and it used to work fine but now it doesn't mount /home2 on /home on boot up. I can manually mount it but then it gets confused and thinks it's mounted on /home2 when it's not. Evidently something must have changed since 4.4-S because it worked until today. on NFSD: (/etc/exports) /home2 -maproot=0 -alldirs httpd on HTTPD: (/etc/fstab) NFSD:/home2 /home nfs rw,bg 0 0 manually mounting mount NFSD:/home2 /home [EMAIL PROTECTED]:~ -13:55:06- # cd ~dkdesign -su: cd: /home2/dkdesign: No such file or directory Not surprising, because you mounted on /home not /home2. [EMAIL PROTECTED]:~ -13:58:45- # cd /home/dkdesign/ [EMAIL PROTECTED]:/home/dkdesign -14:02:21- # ls -al drwxr-xr-x 2 dkdesign dkdesign 512 Mar 13 09:15 public_html/ Yes - that's /home, only /home2 is failing... Works as designed. From /var/log/httpd-error.log: [Wed Jun 4 13:56:45 2003] [error] [client xxx.xxx.xxx.xxx] File does not exist: /home2/dkdesigns/public_html/ I don't get it. Any help? ed /etc/fstab /home2 s/home/home2/ This should be s/home2/home/ or it'll have a line with home22 -- Josh w q -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS Problems FreeBSD -- Solaris
;), Thu, Sep 19, 2002 at 05:58:43PM +, Weston M. Price said that hi all i have several problem but with IPv6 my box and solaris box was comunicationg with IPv6 but nfs not ;( try to set IPs in IPv4 format not IPv6 or hostname for example mount not for kripel.studnet.sk but 193.87.12.67 and so on Hello, I am attempting to mount a few directories from my Solaris machine(s) to my FreeBSD workstation. nfsd is clearly running on Solaris and the sharing the directories is not a problem. When I attempt to mount the directories on FreeBSD I get the following error: damascus:/usr/wmprice: RPCMNT: clnt_create: RPC: Program not registered that's it send me your /etc/exports if i'm wrong replace hostnames and get there IPv4 adreses A simple ps -x | egrep shows that nfsiod is running ps -x | egrep nfsiod 98 ?? I 0:00.00 nfsiod -n 4 99 ?? I 0:00.00 nfsiod -n 4 100 ?? I 0:00.00 nfsiod -n 4 101 ?? I 0:00.00 nfsiod -n 4 I have this configured to begin at startup. So, what am I doing wrong? This would seem to me to be a pretty simple procedure. Any help would be appreciated. Weston To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message\ bye -- 17:08 up 3 days, 19:49, 16 users, load averages: 0,15 0,07 0,02 -- FreeBSD 5.0-CURRENT #15: root@kripel:/usr/src/sys/i386/compile/angel -- powered by [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NFS Problems FreeBSD -- Solaris
In the last episode (Sep 19), Weston M. Price said: I am attempting to mount a few directories from my Solaris machine(s) to my FreeBSD workstation. nfsd is clearly running on Solaris and the sharing the directories is not a problem. When I attempt to mount the directories on FreeBSD I get the following error: damascus:/usr/wmprice: RPCMNT: clnt_create: RPC: Program not registered Make sure rpcbind, mountd, and nfsd are running on the Solaris box. If they are, what does the output of rpcinfo -p damanscus print? -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
