FS#41200 - [linux] 3.15.x btrfs hangups with different oops in run_delalloc_range
Attached to Project:
Arch Linux
Opened by Daniele C. (legolas558) - Monday, 14 July 2014, 20:10 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 06 October 2014, 14:19 GMT
Opened by Daniele C. (legolas558) - Monday, 14 July 2014, 20:10 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 06 October 2014, 14:19 GMT
|
Details
I noticed this issue in Firefox because it would hang up and
then the process would never possibly be terminated (not
even on reboot/shutdown).
The fact processes cannot be terminated causes partitions to not be mounted correctly and disk writes to be forgotten (this can't be any good: it's data loss). Symptoms: - firefox/thunderbird (and I assume it could happen also with other disk intensive applications) will hang up indefinitively, rest of the system works as expected and if you don't go to check the tail of journalctl your will never notice a thing (risky!) Most crashes happen on run_delalloc_range I cannot report any other data corruption/loss than those due to bad unmounting; I am using LUKS and btrfs. See attachment for some of the crashes in kworker/thunderbird (the others for firefox are all alike). |
This task depends upon
I have currently downgraded to 3.14.6-1 as a workaround
We cannot help you here.
https://gist.github.com/cgtx/49d001f72e03e2e3083e
Daniele, were you able to make contact with any btrfs developers?
Everyone that complained was also running LUKS/dm-crypt – see the thread on the linux-btrfs mailing list. Maybe this isn't even related to btrfs?
-> http://www.spinics.net/lists/linux-btrfs/msg34586.html
I reverted to 3.14.6 for now, let's see if that helps.
I'd really like to know what's going on there...
I have no such messages anymore after downgrading to 3.14.6-1
@tpowa I think there should be major news about this bug and possibly 3.15 should be retired
@cgtx perhaps LUKS just increases the likelihood of triggering the bug, wouldn't be the first time..
Btw, on linux-btrfs there was a hint about disabling LZO. Got no deadlock since I disabled compression (but I'm on mainline 3.16-rc6 for now).
I disabled LZO compression in the mount options as Felix mentioned above, and that seems to have fixed the issue for now on 3.15.5-2 (or rather, worked around it).