Date: Tue, 17 Feb 2004 20:36:57 +0100 From: Harald Schmalzbauer <h@schmalzbauer.de> To: Dan Nelson <dnelson@allantgroup.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: NFS server broken for -current Message-ID: <40326D59.6070901@schmalzbauer.de> In-Reply-To: <20040217171503.GK15700@dan.emsphone.com> References: <40318AD2.2020104@schmalzbauer.de> <20040217043442.GA8434@xor.obsecurity.org> <403210F5.6030303@schmalzbauer.de> <20040217171503.GK15700@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBB4B32E8F6E8B1A83BCB2EFF Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dan Nelson schrieb: > In the last episode (Feb 17), Harald Schmalzbauer said: > >>Kris Kennaway schrieb: >> >>>On Tue, Feb 17, 2004 at 04:30:26AM +0100, Harald Schmalzbauer wrote: >>> >>>>some weeks ago I found that when connecting from a linux client to >>>>-a current NFS server the connection "locks" up. Now I have decided >>>>to try again and I have a new box where I can do tests. This >>>>problem still exists for -current from 14.Feb. >>>> >>>>I saw that systat -vm still shows disk traffic (about 7Mb/s) while >>>>em0 (my NIC) only reports 5 interrupts. There's no traffic on the >>>>wire but disk is writing? (I'm sure there's no other process which >>>>could cause disk usage!) Also Sys usage is reported to be 44%! >>>> >>>>Let me know how I can help. NFS really should work again asap. >>> >>>http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/56461 >> >>Oh, _very_ interesting. >> >>Does only FreeBSD > 5.1 use 16-byte cookies? I have a 4.9 box which >>works fine with Linux and if I remember correctly 5.1 also haven't had >>this incompatibility. > > > 4.x clients don't do locking at all. Lock requests always return > success without checking with the server. 4.x servers do handle client > locks, though. > > I don't think kern/56461 should get committed; the bug is in the Linux > kernel, and should be fixed there. At the very least the Linux kernel > should reject the locking request instead of simply dropping it. > > Anyhow, none of that applies to you; it only affects a FreeBSD client > trying to lock a file on a Linux server. You're going the other way > around, right? I'd say run strace on the Linux program and find out You are right. Seems I didn't read carefully enough. > what syscall it's hanging on, and run tcpdump or tethereal to determine > whether it's really an NFS request that's failing. > > >>But what about that mystiq disk access? It's not so funny to see my >>3ware controler (the LED) accessing disks while no process is running >>(shown) which would cause it. > > > Swapping? > Absolutely not. Now swap in use. No running userland process. Nothing. And like I said this problem only occurs with past 5.1 so I don't think debugging the linux box would help. How can I find out what the FreeBSD kernel really does when it claims to use 44% Sys and writes to disk? The LED on from my 3ware controller also flashes so there _is_ data written (or read?) but not from NFS over the wire. Very strange to me Thanks, -Harry --------------enigBB4B32E8F6E8B1A83BCB2EFF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFAMm1dBylq0S4AzzwRApn9AKCQ6sNxr1Jl8CA1eexfHXr2P+SkQQCfZU+W t1PCdg7qnXZwUQ6+8ReFX3c= =ltn4 -----END PGP SIGNATURE----- --------------enigBB4B32E8F6E8B1A83BCB2EFF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40326D59.6070901>