On Thu, 2003-03-27 at 12:24, Steve Sizemore wrote:
> On Thu, Mar 27, 2003 at 12:09:28AM -0800, Terry Lambert wrote:
> > Steve Sizemore wrote:
> > > On Wed, Mar 26, 2003 at 12:18:11AM -0800, Terry Lambert wrote:
> > > > In fact, the only legitimate argument I have ever heard for UDP
> > > > has been
On Thu, Mar 27, 2003 at 12:09:28AM -0800, Terry Lambert wrote:
> Steve Sizemore wrote:
> > On Wed, Mar 26, 2003 at 12:18:11AM -0800, Terry Lambert wrote:
> > > In fact, the only legitimate argument I have ever heard for UDP
> > > has been "I have an old Linux install that can't talk TCP, as
> > > o
Steve Sizemore wrote:
> On Wed, Mar 26, 2003 at 12:18:11AM -0800, Terry Lambert wrote:
> > In fact, the only legitimate argument I have ever heard for UDP
> > has been "I have an old Linux install that can't talk TCP, as
> > only UDP was implemented at the time I installed it".
>
> Have you alread
On Wed, Mar 26, 2003 at 12:18:11AM -0800, Terry Lambert wrote:
>
> In fact, the only legitimate argument I have ever heard for UDP
> has been "I have an old Linux install that can't talk TCP, as
> only UDP was implemented at the time I installed it".
Hi, Terry -
Have you already forgotten the lo
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>Ian Dowse wrote:
>> 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.
>
>This is arguably a bug in the FreeBSD UD
Ian Dowse wrote:
> >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:
Dan Nelson wrote:
> UDP works just fine on a switched network. On my NFS servers I use an
> 8k rsize/wsize and UDP mounts on everything and have relatively few
> dropped fragments.
I'm not sure Ian's network is as reliable. 8-).
Nevertheless, you really do not want to use UDP for NFS with
a pac
In the last episode (Mar 25), Terry Lambert said:
> Ian Dowse wrote:
> > 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 ar
Ian Dowse wrote:
> 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 NF
I'm not sure if it's related, but i've noticed under HEAVY nfs load my
nfs server hangs for a while, then it REBOOTS! i'm pretty sure it's a
nfs related problem, because doing heavy disk i/o on the server itself
doen't have any related problems at all.. only when it's heavy access
over nfs.
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:
Hi,
are there any known issues with NFS-mounts using UDP? I'm seeing some
weird behaviour with a NFS-server (-current as of today).
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
12 matches
Mail list logo
