Re: Background corrections don't show up in device stats, and have low syslog priority. How do I reliably find out about them?

On 4/17/2015 at 10:36 PM, Holger Hoffstaette holger.hoffstae...@googlemail.com wrote: I don't know about the device stats, but at least the log level for read errors was already fixed in a patch series: http://www.spinics.net/lists/linux-btrfs/msg40556.html This was merged into 4.0. Thanks!

Background corrections don't show up in device stats, and have low syslog priority. How do I reliably find out about them?

I've been running some simple tests in a virtual machine with btrfs raid1 and I found the background correction behaviour to be a bit surprising. I've set up a raid1 and stored a big file along with its sha256sum on the volume. If I manually corrupt one of the underlying devices and run a btrfs

Re: Background corrections don't show up in device stats, and have low syslog priority. How do I reliably find out about them?

On Fri, 17 Apr 2015 21:46:08 +0200, ivarun_ml wrote: But if I instead just read the file, then btrfs will still detect and correct the corruption, but the device stats are not updated, and the errors in the syslog have info-priority, making them much harder to notice. [..] I don't know about