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

Groups > linux.debian.kernel > #65118 > unrolled thread

Bug#940105: linux: serious corruption issue with btrfs

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#65118 — Bug#940105: linux: serious corruption issue with btrfs

[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

[toc] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web