In message <[EMAIL PROTECTED]>, Patric Mrawek writes: >On several clients (-DP1, -DP2, 4-stable) mounting a nfs-share >(mount_nfs -i -U -3 server:/nfs /mnt) and then copying data from that >share to the local disk (find -x -d /mnt | cpio -pdumv /local) results >in lost NFS-mount. > >client kernel: nfs server server:/nfs: not responding 10 > 9
I'm not sure what you mean by a "lost" mount. Do all further accesses to the filesystem hang? It is normal enough to get the above 'not responding' errors occasionally on a busy fileserver, but only if they are almost immediately followed by 'is alive again' messages. If the filesystem stops working and doesn't recover, could you run `tcpdump -nepX -s 1600 udp port 2049' when it hangs and record a few packets? Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
