From owner-freebsd-current@FreeBSD.ORG Thu Jul 8 13:58:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 796C416A4CE for ; Thu, 8 Jul 2004 13:58:15 +0000 (GMT) Received: from black3.imgsrc.co.jp (black3.imgsrc.co.jp [210.226.20.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C4D843D46 for ; Thu, 8 Jul 2004 13:58:12 +0000 (GMT) (envelope-from kuriyama@imgsrc.co.jp) Received: from localhost (localhost [127.0.0.1]) by black3.imgsrc.co.jp (Postfix) with ESMTP id CF37F50C12 for ; Thu, 8 Jul 2004 22:58:04 +0900 (JST) Received: from black3.imgsrc.co.jp (black3.imgsrc.co.jp [IPv6:2001:218:422:2::9999]) by black3.imgsrc.co.jp (Postfix) with ESMTP id 6F4D450C0D for ; Thu, 8 Jul 2004 22:58:03 +0900 (JST) Date: Thu, 08 Jul 2004 22:58:03 +0900 Message-ID: <7mk6xey51w.wl@black3.imgsrc.co.jp> From: Jun Kuriyama To: Current User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd 0.1 Subject: NFS over IPv6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2004 13:58:15 -0000 With today's kernel, I see strange behavior with NFS over IPv6. My userland is two days older. I'll check with sync'ed kernel/userland tomorrow. # NFS server is 5.2.1R, client is current. When I did some write operation, it may wait too long. I can sometimes write without problem, but sometimes not. I took tcpdump -vvv: 22:48:25.128338 2001:218:422:2::XXXX > 2001:218:422:2::YYYY: frag (0xdf59d78f:0|1448) 2001:218:422:2::XXXX.1516376639 > 2001:218:422:2::YYYY.2049: 1440 write fh 1034,59016/16299072 4586 bytes @ 0xc000 [flowlabel 0x56097] (len 1456, hlim 64) 22:48:25.128371 2001:218:422:2::XXXX > 2001:218:422:2::YYYY: frag (0xdf59d78f:1448|1448) [flowlabel 0x56097] (len 1456, hlim 64) 22:48:25.128405 2001:218:422:2::XXXX > 2001:218:422:2::YYYY: frag (0xdf59d78f:2896|1448) [flowlabel 0x56097] (len 1456, hlim 64) 22:48:25.128430 2001:218:422:2::XXXX > 2001:218:422:2::YYYY: frag (0xdf59d78f:4344|400) [flowlabel 0x56097] (len 408, hlim 64) 22:48:25.129335 2001:218:422:2::YYYY.2049 > 2001:218:422:2::XXXX.1516376639: reply ok 160 write PRE: sz 0xd1ea mtime 1089294496.000000 ctime 1089294496.000000 POST: REG 664 ids 1000/1000 sz 0xd1ea nlink 1 rdev 199/65077248 fsid 0x420 fileid 0xf8b440 a/m/ctime 1089287695.000000 1089294502.000000 1089294502.000000 4586 bytes (len 168, hlim 64) 22:48:25.129489 2001:218:422:2::XXXX > 2001:218:422:2::YYYY: [icmp6 sum ok] icmp6: 2001:218:422:2::XXXX udp port 829 unreachable (len 216, hlim 64) I don't know why client side replied as port unreachable. With IPv4, there is no problem. -- Jun Kuriyama // IMG SRC, Inc. // FreeBSD Project