Date: Mon, 29 Mar 2021 10:38:01 +0200 From: Stefan Esser <se@freebsd.org> To: Mateusz Guzik <mjguzik@gmail.com> Cc: Andriy Gapon <avg@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: Strange behavior after running under high load Message-ID: <d9b2d38f-a06c-d964-58ce-93e0f482bbe4@freebsd.org> In-Reply-To: <CAGudoHFQN6EkR2Y33sKwbooUGqP-oLJ0yqjpL3HuE7gn7vRLPQ@mail.gmail.com> References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org> <e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org> <c64447e2-4ed4-a948-e15a-efcd66c271a9@freebsd.org> <CAGudoHFQN6EkR2Y33sKwbooUGqP-oLJ0yqjpL3HuE7gn7vRLPQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6AdxU7fH8YRhgoCui7OIAS8FUEehq7tRl
Content-Type: multipart/mixed; boundary="hnayO1vGp4maBnEU3tzQrH5k9P6ufjuVT";
protected-headers="v1"
From: Stefan Esser <se@freebsd.org>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: Andriy Gapon <avg@freebsd.org>,
FreeBSD CURRENT <freebsd-current@freebsd.org>
Message-ID: <d9b2d38f-a06c-d964-58ce-93e0f482bbe4@freebsd.org>
Subject: Re: Strange behavior after running under high load
References: <58bea0f0-5c3d-4263-ebee-f939a7e169e9@freebsd.org>
<e8398b06-de30-63a8-94b1-a336ed32ed27@FreeBSD.org>
<c64447e2-4ed4-a948-e15a-efcd66c271a9@freebsd.org>
<CAGudoHFQN6EkR2Y33sKwbooUGqP-oLJ0yqjpL3HuE7gn7vRLPQ@mail.gmail.com>
In-Reply-To: <CAGudoHFQN6EkR2Y33sKwbooUGqP-oLJ0yqjpL3HuE7gn7vRLPQ@mail.gmail.com>
--hnayO1vGp4maBnEU3tzQrH5k9P6ufjuVT
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Am 29.03.21 um 03:11 schrieb Mateusz Guzik:
> This may be the problem fixed in
> e9272225e6bed840b00eef1c817b188c172338ee ("vfs: fix vnlru marker
> handling for filtered/unfiltered cases").
My system was up for less than 24 hours and using a kernel and world
built on the latest -CURRENT of less than 1 hour before the reboot:
FreeBSD 14.0-CURRENT #33 main-n245694-90d2f7c413f9-dirty: Sat Mar 27 15:3=
5:37=20
CET 2021
The fix had been committed some 9 days before that kernel was built.
> However, there is a long standing performance bug where if vnode limit
> is hit, and there is nothing to reclaim, the code is just going to
> sleep for one second.
There are no log entries that give any hint to what occurred.
But I do assume that these events are not logged ... (?)
Yes, I could have checked that and will do so if the issue occurs
again. I plan to generate more output files in the same way that
triggered the issue yesterday, and since the system is very slow
but still able to execute commands, I can try to debug it, just
have to know where to start looking ...
Thank you for your reply!
Regards, STefan
--hnayO1vGp4maBnEU3tzQrH5k9P6ufjuVT--
--6AdxU7fH8YRhgoCui7OIAS8FUEehq7tRl
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsB5BAABCAAjFiEEo3HqZZwL7MgrcVMTR+u171r99UQFAmBhkekFAwAAAAAACgkQR+u171r99USX
KwgAsC3bOXtdQnd5wFdvUy7fycAJTpNvEhIgsWaq2zrzzOVIIUchVH/GnwqIdX9FY518bJVF3chb
oEG9A/RKn9Cj7rgimqN6kzTc5O7PnulqCMp+RxiFyUD2Q8zjR38PBBmdXUcXyQBoaP5WY5IH94JH
9guPTvJV2dvmFSA7csHarEh6JJLe9gTqTLMueknv7UDcjnUy1AFPDV/sC9TdcJ/vJr6aJeIrajdO
e3eZW284YQ96npeNKEba6L2QMJizvM++yr7JpdZfQy1chqce0DLi/by9UKm9kJXQqUFx2y8zk6uY
FtelYkBjcIdzSwetZzAAeRYRaGdTxqRwCef5kCoSyw==
=rgFo
-----END PGP SIGNATURE-----
--6AdxU7fH8YRhgoCui7OIAS8FUEehq7tRl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d9b2d38f-a06c-d964-58ce-93e0f482bbe4>