On Fri, 26 Jul 2013 15:14:17 -0700 (PDT) Barney Cordoba
wrote about Re: Recommendations for 10gbps NIC:
BC> I don't really understand why nearly all 10GBE cards are dual-port.
BC> Surely there is a market for NICs between 1 gigabit and 20 gigabit.
Myricom has single port 10G cards. However, I on
On Fri, 25 Apr 2014 09:48:36 +0200 Marek Salwerowicz
wrote about NFS over LAGG / lacp poor performance:
Hello Marek,
MS> FreeBSD storage1 9.1-RELEASE-p10 FreeBSD 9.1-RELEASE-p10 #0: Sun Jan 12
MS> 20:11:23 UTC 2014
MS> r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
S
On Fri, 25 Apr 2014 13:34:06 +0200 Marek Salwerowicz
wrote about Re: NFS over LAGG / lacp poor performance:
GK> irq256: igb0:que 0 99396134 64
GK> irq257: igb0:que 1 61496018 39
GK> irq258: igb0:que 2 101687742 66
GK> irq259: igb0:qu
On Fri, 25 Apr 2014 15:02:15 +0100 "Steven Hartland"
wrote about Re: NFS over LAGG / lacp poor
performance:
SH> We find that large numbers of queues causes high interrupt issues
Like the thing I am seeing with igb1 on my system?
---
root@storage:/root #vmstat -i
interrupt
On Fri, 25 Apr 2014 15:25:04 +0100 "Steven Hartland"
wrote about Re: NFS over LAGG / lacp poor
performance:
SH> We saw the issue with 10-RELEASE last weekend on a machine with 6 x
SH> igb's where by the system was burning CPU in the interrupt handlers,
SH> setting num_queues to 2 fixed the issue
On Fri, 25 Apr 2014 15:55:29 +0100 "Steven Hartland"
wrote about Re: NFS over LAGG / lacp poor
performance:
SH> Run top then enable system processes (shift+S) and threads (shift+H)
SH> then disable idle process display (z) if your seeing significant CPU
SH> usage to the igb interrupt handlers try
Hi all,
I just tried to block multicast and broadcast packets on a transparent
bridge with pf by filtering on one of the physical interfaces like this:
table persist {10.117.255.255/32}
netbios = "netbios-ns, netbios-dgm, netbios-ssn, mdns, ipp"
block quick on $ext_if proto ipv6
block quick on $
Hi all,
I get the error message above when trying to go for jumbo frames (mtu
9000) on a system here. I found a lot of comments on this, but they all
state that this is due to a too low setting for mbufs in FreeBSD8/9
settings.
However, I have 10-stable here, and the settings look rather high to m
On Fri, 21 Nov 2014 08:22:31 -0800 Jack Vogel wrote
about Re: igb Could not setup receive structures (again):
JV> After you get the error do a `netstat -m` and see what the state of the
JV> 9K jumbo pool is, for that is the size you would be using.
Hm...
---
root@mclane:~ # netstat -m
20472/337
On Fri, 21 Nov 2014 13:01:23 -0800 Jack Vogel wrote
about Re: igb Could not setup receive structures (again):
JV> Yes, its strange, the mbuf resources look fine.
JV> Can you show the dmesg record from a boot that
JV> includes the failure please?
Well, the machine is in production, I cannot boot
Hi all,
I ran into some weird issue here last week:
I have an NFS-Server for storage and diskless booting (pxe / nfs root)
running under FreeBSD. The clients are running Gentoo Linux. Some time
ago, I replaced the server, going from a HDD-based storage array (ZFS)
under FreeBSD 8.3 to an SSD-based
On Mon, 15 Dec 2014 15:59:29 -0500 (EST) Rick Macklem
wrote about Re: compiling on nfs directories:
RM> Also, note that he didn't see the problem with FreeBSD8.3, which would
RM> have been following the same rules on the server as 10.1.
RM>
RM> What I suspect might cause this is one of two thin
On Thu, 18 Dec 2014 19:05:24 -0500 (EST) Rick Macklem
wrote about Re: compiling on nfs directories:
RM> avg@ just MFC'd a one line ZFS patch (the one I vaguely remembered
RM> before). It is r275401 in head:
RM>
https://svnweb.freebsd.org/base/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/z
On Fri, 19 Dec 2014 08:02:54 -0500 (EST) Rick Macklem
wrote about Re: compiling on nfs directories:
RM> avg@ MFC'd this patch to stable/9 and stable/10, so you can set up a
RM> test machine with stable/10 on it instead of adding the one line
RM> patch to whatever version you are running, if you'd
Hi all,
We have a recent FreeBSD 10.1 installation here that is supposed to act as
nfs (v3) client to an Oracle x4-2l server running Soalris 11.2.
We have Intel 10-Gigabit X540-AT2 NICs on both ends, iperf is showing
plenty of bandwidth (9.xGB/s) in both directions.
However, nfs appears to be terr
On Thu, 25 Jun 2015 12:56:36 -0700 Scott Larson wrote
about Re: NFS on 10G interface terribly slow:
SL> We've got 10.0 and 10.1 servers accessing Isilon and Nexenta via
SL> NFS with Intel 10G gear and bursting to near wire speed with the stock
SL> MTU/rsize/wsize works as expected.
That sou
On Thu, 25 Jun 2015 20:49:11 -0400 (EDT) Rick Macklem
wrote about Re: NFS on 10G interface terribly slow:
RM> Recent commits to stable/10 (not in 10.1) done by Alexander Motin
RM> (mav@) might help w.r.t. write performance (it avoids large writes
RM> doing synchronous writes when the wcommitsize
On Fri, 26 Jun 2015 20:42:08 -0400 (EDT) Rick Macklem
wrote about Re: NFS on 10G interface terribly slow:
RM> Btw, can you tell us what Intel chip(s) you're using?
I have
ix0@pci0:5:0:0: class=0x02 card=0x00028086 chip=0x15288086 rev=0x01
hdr=0x00 vendor = 'Intel Corporation'
device
On Fri, 26 Jun 2015 19:58:42 -0400 (EDT) Rick Macklem
wrote about Re: NFS on 10G interface terribly slow:
RM> The default (auto tuned) value is reported by "nfsstat -m".
RM> It can be set with a mount option (should be something in "man
RM> mount_nfs"). If you are doing a test with 1 megabyte wr
Hi all,
I see some weird (I think) NFS issue here:
I have a NFS server running 10.2-RELEASE exporting a directory to a NFS
client running 10.2-STABLE (as of yesterday, tried that update from 10.1
to see if it would fix this issue, but it stayed with me). I use rsync on
the client to copy data from
On Wed, 4 Nov 2015 14:43:54 +0100 Gerrit Kühn
wrote about strange nfs/rsync stalls:
> I have a couple of other machines that use the same server in the same
> way, none of them ever showed this behaviour. Are there any
> suggestions how to debug/fix this?
Some more pointers from my si
Hello,
I have two stories to tell meanwhile, the first comes here in form of a
forward from a question I posted on the discussion list for dnsmasq
(ports/dns/dnsmasq):
---
Begin forwarded message:
Date: Wed, 27 Feb 2008 09:28:28 +
From: Simon Kelley <[EMAIL PROTECTED]>
To: Gerri
Hello all,
As I got no response at all on freebsd-fs, I try again here...
Begin forwarded message:
Date: Tue, 5 Dec 2017 09:04:51 +0100
From: Gerrit Kühn
To: freebsd...@freebsd.org
Subject: 100.chksetuid handging on nfs mounts
Hello all,
I just found that the daily security job on a
On Fri, 15 Dec 2017 07:08:48 -0700 Alan Somers wrote
about Re: Fw: 100.chksetuid handging on nfs mounts:
Dear Alan,
> This is a known bug. It happens when an NFS filesystem is mounted on the
> same mountpoint as a local filesystem. It's fixed by [1] and MFCed by
> [2] and [3]. What version ar
On Fri, 15 Dec 2017 15:46:59 +0100 Gerrit Kühn
wrote about Re: Fw: 100.chksetuid handging on nfs mounts:
Hello all,
Sorry for picking this up after such a long time...
> > This is a known bug. It happens when an NFS filesystem is mounted on
> > the same mountpoint as a local files
On Thu, 30 Aug 2018 07:25:54 -0600 Alan Somers wrote
about Re: Fw: 100.chksetuid handging on nfs mounts:
> > Any ideas why this happens (and how to prevent it)?
> I just checked, and on my system find does not descend into NFS
> directories mounted under /net. Could you share the output of "mou
On Thu, 30 Aug 2018 08:07:52 -0600 Alan Somers wrote
about Re: Fw: 100.chksetuid handging on nfs mounts:
> Well that's not very illuminating. I was wondering if it had weird mount
> options or something. Are you sure that's why find is hanging? What
> happens if you unmount and repeat the comm
On Thu, 30 Aug 2018 08:07:52 -0600 Alan Somers wrote
about Re: Fw: 100.chksetuid handging on nfs mounts:
> Well that's not very illuminating. I was wondering if it had weird mount
> options or something. Are you sure that's why find is hanging? What
> happens if you unmount and repeat the comm
On Fri, 31 Aug 2018 11:19:02 + Rick Macklem
wrote about Re: Fw: 100.chksetuid handging on nfs mounts:
> >find command with nfs mounted and nfs-nic down: hangs
> Without a functioning network, NFS just keeps trying to do the RPC.
> This is normal behaviour for NFS and has been since 1985.
My
Hello,
I set up a pretty basic unbound service on FreeBSD 11.2 (based on the
default "local" service) that works fine for me as far as I can see (all
names are resolved etc.).
However, in the unbound logfile I see these messages repeated every minute:
---
Mar 26 11:08:37 unbound[66291:0] error: r
On Tue, 26 Mar 2019 11:28:50 +0100 Gerrit Kühn
wrote about unbound error messages:
> Any idea what the error messages might mean? Or are they somewhat bogus
> (with all the 0s in there)?
Duh, it's all my fault: I forgot that I had the monitoring system not only
check the port availa
Hi,
I have two FreeBSD boxes running mediatomb and minidlna. I also have a
couple of clients, mostly internet radios by different manufacturers
(Sangean, Philips, Renkforce...).
I have the (weird) issue that neither mediatomb nor minidlna appears to see
the multicasts discovery messages (not even
On Fri, 15 Jan 2016 15:44:42 +0100 Guido Falsi
wrote about Re: upnp/dlna:
GF> Could you try the patch here:
GF> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205430
I'll try and report back, thanks for the pointer.
GF> I think you're seeing that same issue.
I did not look into the report t
On Fri, 15 Jan 2016 16:54:04 +0100
Guido Falsi wrote:
GF> I forget one thing, Are the mindlna and mediatomb installed in a
GF> jail?
No jails involved here, they are both running on a plain machine.
I just tried the patch you referred to. It applied and compiled
cleanly, but does not change any
On Fri, 15 Jan 2016 23:00:05 +0300
Rozhuk Ivan wrote:
RI> PF by default drop all ip packets with options.
RI> IGMP use ip options -> pf drop all igmp.
Yes, sure, but pf is off here.
cu
Gerrit
___
freebsd-net@freebsd.org mailing list
https://lists.f
On Fri, 15 Jan 2016 21:36:15 +0100
Guido Falsi wrote:
GF> From your description it looks like a different issue. Looks like
GF> some network issue, maybe some network device (switch or router) is
GF> eating up certain multicasts?
There is only one (rather simple, non-smart) switch invloved here,
On Sat, 16 Jan 2016 11:10:02 +0100
Ben Woods wrote:
BW> I would test the WLAN access point, and make sure it is passing
BW> multicast traffic between the wired and wireless interfaces.
I had already tested that by using cables instead of WLAN (most of my
radios have an extra ethernet port). But
Hi all,
Half a year ago we had reported here about issues with ix-interfaces when
transporting data over nfs. We only got about 50MByte/s back then, and
were not able to fix this issue. Instead, we went for rsyncd transport
that gave us about 200MByte/s (still not the full bandwidth, but
definitel
Hi all,
I already reported this issue here a year ago and unfortunately was not
able to fix it back then. Now I had another run at it, using two recent
10.3-machines with a direct 10G link. I still see nfs is painfully
slow (around 20-80MB/s). I tried both nfsv3 and nfsv4, with almost the same
res
On Tue, 2 Aug 2016 08:45:07 -0600 Alan Somers wrote
about Re: NFS on 10G interfaces still painfully slow:
> > Is there anyone around here who can confirm that nfs can go faster
> > over 10G links?
> > Any hints for further tuning/debugging are greatly appreciated.
AS> I can get 1GB/s over NFS on
On Wed, 3 Aug 2016 07:59:54 +0200 Gerrit Kühn
wrote about Re: NFS on 10G interfaces still painfully slow:
GK> 1048576000 bytes transferred in 1.403620 secs (747051194 bytes/sec)
GK> 1048576000 bytes transferred in 1.380546 secs (759537249 bytes/sec)
Argh! ;-)
Obviously, I cannot re
Hi all,
Over the last weekend, I saw a couple of crashes on a 10.3-system acting
as filtering bridge with pf that all looked like this:
---
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xe
fault cod
On Wed, 21 Sep 2016 16:22:14 +0200 Gerrit Kühn
wrote about igb/pf-related crashes:
[...]
> #17 0x8091c99b at intr_event_execute_handlers+0xab
Few more details:
---
#0 doadump (textdump=) at pcpu.h:219
219 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) #0 doad
Hello,
I have a set of NFS(v3) client/server machines which have been working fine
for me for the last years. However, lately the client side sometimes
complains about:
---
Jul 15 01:41:55 client kernel: nfs server server:/data:
lockd not responding
Jul 15 01:41:55 client kernel: nfs server serve
44 matches
Mail list logo
