On 2019/10/27 上午12:30, Christian Pernegger wrote:
> Am Sa., 26. Okt. 2019 um 16:07 Uhr schrieb Qu Wenruo <quwenruo.btrfs@xxxxxxx>:
>> Mind to share the csum error log?
>
> Certainly. That is, you're welcome to it, if you tell me how to
> generate such a thing. Is there an elegant way to walk the entire
> filesystem, trigger csum calculations for everything and generate a
> log? Something like a poor man's read-only scrub?
The csum error can be seen in the kernel message.
So "dmesg" is enough to output them.
To find all csum error, there is the poor man's read-only scrub:
# find <mnt> -type f -exec cat {} > /dev/null \;
Thanks,
Qu
>
>> I'll fix the bug and update the patchset.
>> (Maybe also make btrfs falls back to skipbg by default)
>
> I appreciate it.
>
> Cheers,
> C.
>
Attachment:
signature.asc
Description: OpenPGP digital signature
