nfsuserd + jails mbufs leak ?

Julien Cigar julien at perdition.city
Sat Dec 31 14:59:18 UTC 2016


Hello,

I just upgraded a bunch of machines from 10.0 to 10.3. Those machines
have a lot of jails with NFS shares (mounted on the HOST), for example:

jcigar at HOST:~/ > mount|grep -i 'filer'
filer.prod.lan:/pictures/collections on
/usr/jails/www2/filer/pictures/collection (nfs, read-only, nfsv4acls)
filer.prod.lan:/webapps on /usr/jails/www2/filer/webapps (nfs,
nfsv4acls)
filer.prod.lan:/documents on /usr/jails/www2/filer/documents (nfs,
read-only, nfsv4acls)
filer.prod.lan:/apache on /usr/jails/www2/filer/apache (nfs, nfsv4acls)
filer.prod.lan:/geoserver on /usr/jails/java2/filer/geoserver (nfs,
nfsv4acls)

HOSTs and NFS server have vfs.nfsd.server_min_nfsvers=4
vfs.nfsd.server_max_nfsvers=4 (but it's probably not related to the
problem) and nfsuserd is runnings on each HOST (with no special
${nfsuserd_flags})

On the hosts since I upgraded to 10.3 I'm seeing tons of:
Dec 31 14:29:33 duvel nfsuserd:[675]: req from ip=0xc0a80a21 port=618

It is not clear to me yet why I'm getting this, but from what I 
understand it's because requests are not coming from 127.0.0.1 but from
the jail ip (192.168.10.x in my case).. Parallel to this I'm observing a
constant increase of mbufs usage so that at some point in time I'm
getting an exhaustion of mbufs:

[zone: mbuf] kern.ipc.nmbufs limit reached

.. and the HOST needs a reboot :(

If I'm stopping nfsuserd I don't see any mbuf leakage anymore

Any idea ? :)

Thanks,
Julien

-- 
Julien Cigar
Belgian Biodiversity Platform (http://www.biodiversity.be)
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20161231/243c5a88/attachment.sig>


More information about the freebsd-fs mailing list