diff options
| author | Jaegeuk Kim <jaegeuk@google.com> | 2020-04-23 08:28:35 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@google.com> | 2020-04-23 20:52:11 +0000 |
| commit | 2e5b7c425f82041e3b51fb318df8d8e5de9b9796 (patch) | |
| tree | 6a566bf79342301955588ae41ede99c7d1535f27 /trusty/coverage/coverage.cpp | |
| parent | efe9defc65b2b0c9f6cf3b329dc161190f8efcf9 (diff) | |
logcatd: unset pinning log files
commit 5327d931acc2 ("logcatd: fallocate and fadvise to logcat files")
introduced pinning log files in order to avoid f2fs fragmentation.
But, logcatd does not guarantee to write data within fallocated 2MB space.
So, we can see some bytes written beyond 2MB boundary which results in
pinning small chunks across the filesystem. This makes F2FS GC have to unset
the pinning blocks via GC loop. If this happens during checkpoint=disable
at booting time, we can see long delay to mount /data accordingly.
Bug: 136483670
Bug: 137180754
Bug: 149418646
Fixes: 5327d931acc2 ("logcatd: fallocate and fadvise to logcat files")
Signed-off-by: Jaegeuk Kim <jaegeuk@google.com>
Change-Id: I986221d6d1da9b8e46e63d1be98ddf0ce4cb099f
Diffstat (limited to 'trusty/coverage/coverage.cpp')
0 files changed, 0 insertions, 0 deletions