[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/q/ - Q&A Central

Help, troubleshooting & advice for practitioners
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1787138290289.jpg (139.64 KB, 1024x1024, img_1787138281991_ix9n5d1x.jpg)ImgOps Exif Google Yandex

31b36 No.2120

if ur logs are trailing behind, try using systemctl restart sync-service. service to clear the buffer cache . it's much spoilerfaster than a full reboot.

31b36 No.2121

File: 1787138448456.jpg (133 KB, 1024x1024, img_1787138432559_g65fl9k1.jpg)ImgOps Exif Google Yandex

>>2120
restarting the service works for a quick fix, but you should also check if your io_scheduler is bottlenecking during those spikes. i've had better luck switching to deadline when the disk latency starts climbing.


[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">