Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #65118

Bug#940105: linux: serious corruption issue with btrfs

From Laurence Parry <greenreaper@gmail.com>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#940105: linux: serious corruption issue with btrfs
Date 2019-09-16 11:00 +0200
Message-ID <yGV1v-5MW-3@gated-at.bofh.it> (permalink)
References <yFxaV-6q4-3@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

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, several user
data files supposedly saved during that time. A small but noticeable
increase in iowait accompanied the start of the lost logs and continued
until the hang.

I guess I was lucky we did not lose more - at least, I *hope* not, because
it is hard to be sure of that without a byte-by-byte verification...

Don't know if it is related, but the behaviour of this kernel has also been
to significantly increase the size of the slab cache of dentries/inodes
during rsync, resulting in fragmentation and a massive increase in the
amount of free memory (despite setting vm.vfs_cache_pressure=10000 in an
attempt to remedy it).

I can of course compile my own kernel, but I concur with Christoph's
assessment of this bug's severity and would encourage a new backports
release ASAP.
-- 
Laurence "GreenReaper" Parry - administrator, Inkbunny.net

Back to linux.debian.kernel | Previous | Next | Find similar | Unroll thread


Thread

Bug#940105: linux: serious corruption issue with btrfs Laurence Parry <greenreaper@gmail.com> - 2019-09-16 11:00 +0200

csiph-web