Zach Brown e54f8d3ec0 Don't shutdown server from sending to fencing client ...

Errors from lock server calls typically shut the server down.

During normal unmount a client's locks are reclaimed before the
connection is disconnected.  The lock server won't try to send to
unmounting clients.

Clients whose connections time out can cause ENOTCONN errors.  Their
connection is freed before they're fenced and their locks are reclaimed.
The server can try to send to the client for a lock that's disconnected
and get a send error.

These errors shouldn't shut down the server.  The client is either going
to be fenced and have the locks reclaimed, ensuring forward progress, or
the server is going to shutdown if it can't fence.

This was seen in testing as multiple clients were timed out.

Signed-off-by: Zach Brown <zab@versity.com>

2026-01-13 15:34:55 -08:00

..

src

Don't shutdown server from sending to fencing client

2026-01-13 15:34:55 -08:00

.gitignore

scoutfs: update rpm building infrastructure

2018-09-14 15:07:10 -07:00

Makefile

Require sparse, and filter kernel sparse output

2025-10-03 09:35:36 -07:00

scoutfs-kmod.spec.in

Block EL9 minor version upgrades

2024-12-02 16:04:24 -08:00