On 1/21/19 6:49 AM, Tetsuo Handa wrote: > When something let __find_get_block_slow() hit all_mapped path, it calls > printk() for 100+ times per a second. But there is no need to print same > message with such high frequency; it is just asking for stall warning, or > at least bloating log files. > > [ 399.866302][T15342] __find_get_block_slow() failed. block=1, b_blocknr=8 > [ 399.873324][T15342] b_state=0x00000029, b_size=512 > [ 399.878403][T15342] device loop0 blocksize: 4096 > [ 399.883296][T15342] __find_get_block_slow() failed. block=1, b_blocknr=8 > [ 399.890400][T15342] b_state=0x00000029, b_size=512 > [ 399.895595][T15342] device loop0 blocksize: 4096 > [ 399.900556][T15342] __find_get_block_slow() failed. block=1, b_blocknr=8 > [ 399.907471][T15342] b_state=0x00000029, b_size=512 > [ 399.912506][T15342] device loop0 blocksize: 4096 > > This patch reduces frequency to up to once per a second, in addition to > concatenating three lines into one. Applied, thanks. -- Jens Axboe
