On 2.02.2018 03:28, Janos Toth F. wrote:
> I started seeing these on my d=raid5 filesystem after upgrading to Linux 4.15.
>
> Some files created since the upgrade seem to be corrupted.
>
> The disks seem to be fine (according to btrfs device stats and
> smartmontools device logs).
>
> The res
On Thu, Feb 1, 2018 at 6:37 PM, Janos Toth F. wrote:
> Hmm... Actually, I just discovered a different machine with s=m=d=dup
> (single HDD) spit out a few similar messages (a lot less and it took
> longer for them to appear at all but it handles very little load):
>
> [ 333.197366] WARNING: CPU:
On Thu, Feb 1, 2018 at 6:28 PM, Janos Toth F. wrote:
> I started seeing these on my d=raid5 filesystem after upgrading to Linux 4.15.
>
> Some files created since the upgrade seem to be corrupted.
How are you determining they're corrupt? Btrfs will spit back an I/O
error rather than deliver corru
Hmm... Actually, I just discovered a different machine with s=m=d=dup
(single HDD) spit out a few similar messages (a lot less and it took
longer for them to appear at all but it handles very little load):
[ 333.197366] WARNING: CPU: 0 PID: 134 at fs/fs-writeback.c:2339
__writeback_in
