Hi,
On Wed, Sep 25, 2019 at 02:17:23AM +0200, Christoph Anton Mitterer wrote:
> Hey.
>
> Is there anything one can help to speed this up?
>
> A patch is available for two weeks now, while Debian users of testing
> and unstable are left with the danger of catastrophic btrfs corruption
> without e
Hey.
Is there anything one can help to speed this up?
A patch is available for two weeks now, while Debian users of testing
and unstable are left with the danger of catastrophic btrfs corruption
without even any warning to them (so that they could at least downgrade
to <5.2).
Cheers,
Chris.
I had a look at and it appears to have gone into both 5.3 (final) and
5.2.15.
For what it's worth, it took only a day or so to exhibit the issue on our
(admittedly active) nginx/postgres/PHP server; we weren't doing any unusual
work during that time. If you're using btrfs, and you can't apply a pa
We seem to have run into this yesterday on a production server sing a
custom compile of the 5.2.9 buster-backports kernel. nginx was hung in D
status, sync hung as well, no obvious reason for it; I ended up having to
reset the machine.
On boot I found we had lost several hours of logs and worse, s
Hey.
Just to put some emphasise on this, the fix has now been merged late to
5.3 as urgent.
Also note Filipe's post[0] that the issue can more or less hit anyone.
Cheers,
Chris.
[0]
https://lore.kernel.org/linux-btrfs/9731b0e7-81f3-4ee5-6f89-b4fd8d981...@petaramesh.org/T/#m7b3863ef7ec5f62a2f7
Source: linux
Version: 5.2.9-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss
Hi.
There were some reports over the last weeks from users on linux-btrfs which
suffered from catastrophic btrfs corruption.
The bug which is apparently a regression introduced in 5.2 h
6 matches
Mail list logo
