Date: Mon, 28 Oct 2024 23:40:59 +0000 From: void <void@f-m.fm> To: freebsd-fs@freebsd.org Subject: Re: improving nfs client & server performance Message-ID: <ZyAhC8GGA5zEbK4P@int21h> In-Reply-To: <CAM5tNy5j6RknwbvcXjCDs02r1JEO4_De3mY8JHrxYNb0nKhNrw@mail.gmail.com> References: <ZxZbPmv_11tS5pxZ@int21h> <CAM5tNy4scNutJXdOL=UmK_NhObcfbwpnUpL1dFqe3JVeJVWvcQ@mail.gmail.com> <Zxai_n-LhohogSEY@int21h> <CAM5tNy5j6RknwbvcXjCDs02r1JEO4_De3mY8JHrxYNb0nKhNrw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 21, 2024 at 03:52:12PM -0700, Rick Macklem wrote:
(stuff)
Hi Rick I tried the various things suggested and did notice a performance
improvement. What I'm seeing though right now is the following, in a
different context [1]
login[some_pid] Getting pipebuf resource limit: Invalid argument
[1] context is root creating a tar on a nfs mount. The tar is huge,
over a Tb, as it's backing up homedirs [2]. It seems to be running ok
though. For the mment. But I'm not seeing anything remotely
approaching maximums in netstat -m, and thought with root doing
the backup its resources would be pretty much unlimited.
It's not spamming the console though.
[2] The SMR hd is showing signs it's ill. Slow everything.
Trying to move all the data off there before a (cold) reboot.
Thing is with these SMRs (I've had two) it seems nothing much
happens in the bad blocks sense. it just gets *very* *slow*.
It's zfs, but single disk, 8Tb.
--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZyAhC8GGA5zEbK4P>