4 ms·
I think you would get more mileage out of tracking where all the writes are, and making whatever changes are needed to reduce them. Auditd, can, for example, t
by tyingq 7y ago
I think you would get more mileage out of tracking where all the writes are, and making whatever changes are needed to reduce them.
Auditd, can, for example, track every write. Track it over a good sample period of typical use, then make whatever changes are needed. Might be database tuning, moving specific files to tmpfs, changing the way you do backups, reducing writes to syslog, changing fs mount options, etc.
Auditd is a little complex, but it's fairly easy to find write-ups on how to monitor writes and generate use reports.
- zzzcpan 7y agoYou can just use the find command for tracking writes, for example: find / -type f -printf '%TY-%Tm-%Td %TT %p\n' | sort (you probably want to add -mount in there too and use find per each mount point separately)
- tyingq 7y agoAuditd would show frequency, the process name and uid that did the write, and when, etc. Last modified time isn't always enough.
- cmurf 7y agofatrace https://piware.de/2012/02/fatrace-report-system-wide-file-access-events/ https://piware.de/2012/02/fatrace-report-system-wide-file-ac...