Avoid logspam in f2fs_sparseblock
generate_f2fs_info() prints a lot of DEBUG level messages -- about 155
for a mostly-empty filesystem. But the only caller is vold's
encrypt_inplace(), which just wants to iterate through all the used
blocks. (There's also a cc_binary "f2fs_sparseblock" declared in
Andorid.bp, but nothing seems to use it.) The other filesystem details
aren't really that important. Indeed, the ext4 equivalent is silent.
Avoid this logspam by changing the messages to VERBOSE. This results in
a much cleaner log when initializing metadata encryption at first boot.
Change-Id: I4e57369ba8db6ac2341b70a88570c812dc99d6a8
1 file changed