On Sep 28, 2006, at 1:54 AM, Chad Leigh -- Shire.Net LLC wrote:
On Sep 26, 2006, at 12:26 PM, Chad Leigh -- Shire.Net LLC wrote:On Sep 26, 2006, at 12:24 PM, Mike Kupfer wrote:"Chad" == Chad Leigh <-- Shire.Net LLC" <[EMAIL PROTECTED]>> writes:Chad> snoop does not show me the reply packets going back. What do IChad> need to do to go both ways? It's possible that performance issues are causing snoop to miss the replies.If your server has multiple network interfaces, it's more likely that the server is routing the replies back on a different interface. We've run into that problem many times with the NFS server that has my homedirectory on it. If that is what's going on, you need to fire up multiple instances of snoop, one per interface.OK, I will try that. I did run tcpdump on the BSD client as well so the responses should show up there as well as it only has the 1 interface on that net while the Solaris box has 3.That got me thinking. Since I had 3 "dedicated" ports to use for nfs, I changed it so each is on its own network (192.168.2 .3 . 4) so there is no port switcheroo on incoming and outgoing port. I also upgraded the FreeBSD to catch any bge updates and patches (there were some I think but I am not sure they had anything to do with my issue). Anyway, after doing both of these my issue seems to have gone away... I am still testing / watching but I have not seen or experienced the issue in a day. I am not sure which one "fixed" my problem but it seems to have gone away.
Ok, the problem started again today or yesterday (wed or tuesday) and seems to be "worse" than ever. Some symptoms are different. Before it was just the one specific zfs pool (say local/mail/foo.com/ c/chad ) that was not responding. And, if I remember correctly, I could have a shell on the Solaris side and still do things on the local zfs side -- only the nfs server is not responding. Now, the whole zfs system seems to freeze up and all nfs served pools are unavailable at the same time and I cannot access them independently on the solaris side in a shell (in fact, I cannot even log in during the episodes since my user home directory in in a zfs pool -- /local/ home/chad in the local/home/chad pool). Previously they woujld last 3-10 min. Now they seem to be lasting 15-20 minutes or so.
I do not think this is the whole-pool-sync issue with nfs as it shouldn't take 15-20 minutes to do a sync of the pool (about 1.6-2.0GB across all zfs based pools/FS [about 10, mostly empty or almost empty] on the machine with almost all of that in one pool -- an email store for one account that is about 1.6GB) and it doesn't happen on every file write.
No patches have been applied since I last reported it was OK about a week ago.
Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
