On Thu, Apr 22, 2010 at 02:53:37PM -0700, Rich Teer wrote: > On Thu, 22 Apr 2010, Mike Mackovitch wrote: > > > I would also check /var/log/system.log and /var/log/kernel.log on the Mac to > > see if any other useful messages are getting logged. > > Ah, we're getting closer. The latter shows nothing interesting, but > system.log > has this line appended the minute I try the copy: > > sandboxd[78312]: portmap(78311) deny network-outbound > /private/var/tmp/launchd/sock > > Then, when the attempt times out, these appear: > > KernelEventAgent[36]: tid 00000000 received event(s) VQ_NOTRESP (1) > KernelEventAgent[36]: tid 00000000 type 'nfs', mounted on > '/net/zen/export/home' from 'zen:/export/home', not responding > KernelEventAgent[36]: tid 00000000 found 1 filesystem(s) with problem(s) > > Does that shed any morelight on this?
Nope. The first message is a known annoyance that gets logged whenever portmap starts. It can be ignored. The second message is just the daemon responsible for inducing the "disconnect dialog" noticing that there is an unresponsive file system. Oh, and the kernel.log should at least have the "lockd not responding" messages in it. So, I presume you meant nothing *else* interesting. I think it's time to look at the packets... (...and perhaps time to move this off of zfs-discuss seeing as this is really an NFS/networking issue and not a ZFS issue.) HTH --macko _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
