tree dd5583487f7473851ffedb4314d1815cfb0abb25
parent f6f33713f9e231409522906ad5e77f5bbc772468
author Eric Biggers <ebiggers@google.com> 1604636041 -0800
committer Eric Biggers <ebiggers@google.com> 1604636916 -0800

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