Jaegeuk Kim 63cdd7095b logcatd: unset pinning log files ... commit 5327d931ac ("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: 5327d931ac ("logcatd: fallocate and fadvise to logcat files") Signed-off-by: Jaegeuk Kim <jaegeuk@google.com> Change-Id: I986221d6d1da9b8e46e63d1be98ddf0ce4cb099f		2020-04-23 13:53:37 -07:00
..
tests	liblog: don't return 0xFFFFFFFF as an invalid log id.	2019-03-25 16:41:39 -07:00
Android.bp	logcat: fix logcatd / logpersist	2019-10-31 06:43:47 -07:00
event.logtags	Documented range of event logtags used by Android Automotive.	2020-04-15 14:43:36 -07:00
logcat.cpp	logcatd: unset pinning log files	2020-04-23 13:53:37 -07:00
logcatd	Relax permissions on /data/misc/logd	2020-01-21 18:39:19 -08:00
logcatd.rc	Relax permissions on /data/misc/logd	2020-01-21 18:39:19 -08:00
logpersist	logcat: fix logpersist.stop and logpersist.clear	2019-10-31 06:43:47 -07:00
MODULE_LICENSE_APACHE2
NOTICE
OWNERS	Add OWNERS.	2017-12-07 13:30:03 -08:00