Re: Writeback errors in kernel log with Linux 4.15 (m=s=raid1, d=raid5, 5 disks)

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

Re: Writeback errors in kernel log with Linux 4.15 (m=s=raid1, d=raid5, 5 disks)

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): > > [

Re: Writeback errors in kernel log with Linux 4.15 (m=s=raid1, d=raid5, 5 disks)

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

Re: Writeback errors in kernel log with Linux 4.15 (m=s=raid1, d=raid5, 5 disks)

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

Writeback errors in kernel log with Linux 4.15 (m=s=raid1, d=raid5, 5 disks)

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 rest of the Btrfs filesystems (with m=s=d=single profiles) do