On Fri, 3 Jul 2009, Eric Schrock wrote:
This sneaky line:811: setsockopt(13, tcp, TCP_CORK, 0x08047AC4, 4, SOV_DEFAULT) = 0 ^^^^^^^^As well as the fact that you are using proftpd. The sight of TCP_CORK still triggers some deep fight or flight reaction in my animal brain, after having watched others debug the original problem.
I had never heard of the TCP_CORK socket option before. There is an excellent summmary at "http://www.baus.net/on-tcp_cork";. The decription includes mention that mis-using TCP_CORK could cause a socket hang at the end of the transfer or if the application waits for a response while the kernel is still waiting for more data from the application. It is necessary to remove TCP_CORK before writing the final data and if the application guesses wrong, the connection will hang.
Bob -- Bob Friesenhahn bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
