Re: NFS freeze
On Thu, 12 May 2005 22:03:40 -0500 Kelly D. Grills [EMAIL PROTECTED] wrote: On Fri, May 13, 2005 at 02:52:52AM +0200, Pietro Cerutti wrote: Kelly D. Grills wrote: Have a look at section 23.3.5 of the handbook. -r=1024 cured my problems. Thank you, this solves the problem when mounting manually. What if I used amd to automatically mount the NFS share? I didn't find how to set mount specific options in amd. Well, I've no experience with amd. I took a quick look at amd.conf(5), the selectors_on_default parameter looks like it may be relevant. -- Kelly D. Grills [EMAIL PROTECTED] An excerpt from /usr/src/contrib/amd/doc/am-utils.texi: For example, if the default options specified were @example opts:=rw,nosuid,intr,rsize=1024,wsize=1024,quota,posix @end example You get the idea how to set rsize into opts:=. horio shoichi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NFS freeze
Hi list, I have a problem with a NFS exports: the client freezes while transfering large amount of data. Both client and server are FreeBSD-5.4-RELEASE machines, builded on Tuesday, May 10. Here's some info: --- SERVER --- # /etc/exports /share -maproot=0 -network 192.168.1.0 -mask 255.255.255.248 # relevant lines on /etc/rc.conf rpcbind_enable=YES nfs_server_enable=YES nfs_client_enable=YES mountd_flags=-r # ifconfig rl0 rl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=8VLAN_MTU inet 192.168.1.6 netmask 0xfff8 broadcast 192.168.1.7 inet6 fe80::20e:e8ff:fe8b:2af8%rl0 prefixlen 64 scopeid 0x2 ether 00:0e:e8:8b:2a:f8 media: Ethernet autoselect (100baseTX full-duplex) status: active -- CLIENT -- # ifconfig re0 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=18VLAN_MTU,VLAN_HWTAGGING inet 192.168.1.3 netmask 0xfff8 broadcast 192.168.1.7 inet6 fe80::202:3fff:fe67:fc69%re0 prefixlen 64 scopeid 0x2 ether 00:02:3f:67:fc:69 media: Ethernet autoselect (none) # mount srv-file:share /share/ # tar -cvzf /share/home.tar.gz /home I see the files being added to the archive, after about 8MB (I tried making the archive locally to see the size) the client freezes. I can in no ways kill the tar archiver (killall, kill -9, Ctrl+C don't work) I can't umount the share. I have to brutally shut down the computer. On my share, I see a file name home.tar.gz of size 0 Byte I can't understand what's happening when the client freezes, any help or opinion is appreciated! Thank you very much, best regards! -- Pietro Cerutti - [EMAIL PROTECTED] Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming or what? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS freeze
On Thu, May 12, 2005 at 09:21:39PM +0200, Pietro Cerutti wrote: I have a problem with a NFS exports: the client freezes while transfering large amount of data. snippage Have a look at section 23.3.5 of the handbook. -r=1024 cured my problems. -- Kelly D. Grills [EMAIL PROTECTED] pgpaKQeWryObu.pgp Description: PGP signature
Re: NFS freeze
Kelly D. Grills wrote: Have a look at section 23.3.5 of the handbook. -r=1024 cured my problems. Thank you, this solves the problem when mounting manually. What if I used amd to automatically mount the NFS share? I didn't find how to set mount specific options in amd. Thank you once again! -- Pietro Cerutti - [EMAIL PROTECTED] Windows: Where do you want to go today? Linux: Where do you want to go tomorrow? BSD: Are you guys coming or what? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS freeze
On Fri, May 13, 2005 at 02:52:52AM +0200, Pietro Cerutti wrote: Kelly D. Grills wrote: Have a look at section 23.3.5 of the handbook. -r=1024 cured my problems. Thank you, this solves the problem when mounting manually. I also highly recommend the intr option to all NFS mounts. This largely eliminates the unkillable process problem. -- Clifton -- Clifton Royston -- [EMAIL PROTECTED] Tiki Technologies Lead Programmer/Software Architect I'm gonna tell my son to grow up pretty as the grass is green And whip-smart as the English Channel's wide... -- 'Whip-Smart', Liz Phair ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS freeze
On Fri, May 13, 2005 at 02:52:52AM +0200, Pietro Cerutti wrote: Kelly D. Grills wrote: Have a look at section 23.3.5 of the handbook. -r=1024 cured my problems. Thank you, this solves the problem when mounting manually. What if I used amd to automatically mount the NFS share? I didn't find how to set mount specific options in amd. Well, I've no experience with amd. I took a quick look at amd.conf(5), the selectors_on_default parameter looks like it may be relevant. -- Kelly D. Grills [EMAIL PROTECTED] pgpCijlvHkuza.pgp Description: PGP signature
