Of all the gin joints in all the towns in all the world, Matthew Dillon
had to walk into mine and say:
> And here is something *really* scary. For the last month I've been
> running NFS over TCP without even realizing it. I had set up my
> machines to run NFS/TCP as a test instead of NFS/UDP and then forgot
> to change it back!
>
> -Matt
And here is something even scarier: readdirplus from the client side
doesn't appear to work correctly either. This time, you don't need an
IRIX machine to trigger the problem (though it helps :). Do the following
client# mount -o nvsv3,tcp,rdirplus server:/somefs /mnt
client# ls /mnt; du /mnt; etc...
Seems okay so far, right? Ah, but now try to unmount the filesystem:
# umount /mnt
<process wedges, can't be killed, can't log in, other processes wedge, etc..>
With an IRIX server, the machine wedges as soon as you do ls /mnt. With
a FreeBSD server, nothing happens until you try to unmount the filesystem.
The umount process looks like this:
0 418 388 0 -2 0 312 176 vnlock D+ p0 0:00.01 umount /mnt
When the machine got stuck when I tested it with IRIX, I had to take
a crash dump in order to analyze things; the kernel doesn't seem to
be wedged, but I see these:
1063 362 293 0 -2 0 356 0 vnlock D+ v0 0:00.00 (ls)
1063 318 1 17 -2 17 748 0 vnlock DN p0 0:00.00 (mailck)
Actually, it looks like it wedges if you use UDP too, so I guess it's
not related to the transport.
Anybody have any ideas? I did my good deed for the day.
-Bill
--
=============================================================================
-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu
Work: [EMAIL PROTECTED] | Center for Telecommunications Research
Home: [EMAIL PROTECTED] | Columbia University, New York City
=============================================================================
"It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness"
=============================================================================
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
