frequently more than 300MBytes/second read I/O for influxdb V2.1.7 even all applications had stoped!

__Steps to reproduce:__
List the minimal actions needed to reproduce the behaviour.

[root@prod1 06]# ps -ef|grep influxdb|grep data|grep -v grep
root 2889694 1 71 12:00 ? 05:11:48 /data/ces/evo/influxdb/influxd
[root@prod1 06]# pidstat -d 2 10 -p 2889694
Linux 4.19.90-25.29.v2101.ky10.x86_64 (prod1) 03/23/2024 _x86_64_ (16 CPU)

07:14:57 PM UID PID kB_rd/s kB_wr/s kB_ccwr/s iodelay Command
07:14:59 PM 0 2889694 340794.00 1406.00 0.00 87 influxd
07:15:01 PM 0 2889694 329780.00 2412.00 0.00 50 influxd
07:15:03 PM 0 2889694 388044.00 456.00 0.00 133 influxd
07:15:05 PM 0 2889694 351654.00 2596.00 0.00 163 influxd
07:15:07 PM 0 2889694 349186.00 2296.00 0.00 117 influxd
07:15:09 PM 0 2889694 342432.00 2278.00 0.00 97 influxd

Average: 0 2889694 350315.00 1907.33 0.00 108 influxd
[root@prod1 06]#

we had stoped application ,but pidstat still show high read I/O for influxd process.
kB_rd/s column show 340794 KB read per second!
this problem is happening. we can reproduce it at will.

__Expected behaviour:__
Describe what you expected to happen.

influxdb version : v2.1.7
We want to know what caused it and how to solve it. Thank you

__Actual behaviour:__
Describe What actually happened.

__Environment info:__

* Please provide the command you used to build the project, including any `RUSTFLAGS`.
* System info: Run `uname -srm` or similar and copy the output here (we want to know your OS, architecture etc).
* If you're running IOx in a containerised environment then details about that would be helpful.
* Other relevant environment details: disk info, hardware setup etc.

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.

__Logs:__
Include snippet of errors in logs or stack traces here.
Sometimes you can get useful information by running the program with the `RUST_BACKTRACE=full` environment variable.
Finally, the IOx server has a `-vv` for verbose logging.