Re: Possible deadlock when writing

2018-12-03 Thread Tony Lambiris
I've been running into (what I believe) is the same issue ever since upgrading to 4.19: [28950.083040] BTRFS error (device dm-0): bad tree block start, want 1815648960512 have 0 [28950.083047] BTRFS: error (device dm-0) in __btrfs_free_extent:6804: errno=-5 IO failure [28950.083048] BTRFS info

Re: Possible deadlock when writing

2018-12-01 Thread Martin Bakiev
I was having the same issue with kernels 4.19.2 and 4.19.4. I don’t appear to have the issue with 4.20.0-0.rc1 on Fedora Server 29. The issue is very easy to reproduce on my setup, not sure how much of it is actually relevant, but here it is: - 3 drive RAID5 created - Some data moved to it -

Re: Possible deadlock when writing

2018-12-01 Thread Janos Toth F.
I obviously can't be sure (due to obscure nature of this issue) but I think I observed similar behavior. For me it usually kicked in during scheduled de-fragmentation runs. I initially suspected it might have something to do with running defrag on files which are still opened for appending writes

Possible deadlock when writing

2018-11-26 Thread Larkin Lowrey
I started having a host freeze randomly when running a 4.18 kernel. The host was stable when running 4.17.12. At first, it appeared that it was only IO that was frozen since I could run common commands that were likely cached in RAM and that did not touch storage. Anything that did touch