linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: clonejo <clonejo@shakik.de>
To: Kent Overstreet <kent.overstreet@linux.dev>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	linux-bcachefs@vger.kernel.org
Subject: Re: bcachefs dropped writes with lockless buffered io path, COMPACTION/MIGRATION=y
Date: Tue, 27 Aug 2024 09:57:56 +0200	[thread overview]
Message-ID: <706de714-9293-4d8c-b2bf-f91b87adc313@shakik.de> (raw)
In-Reply-To: <ieb2nptxxk2apxfijk3qcjoxlz5uitsl5jn6tigunjmuqmkrwm@le74h3edr6oy>

On 27/08/2024 05:29, Kent Overstreet wrote:
> Interestingly, it only triggers for QEMU - the test fails pretty
> consistently and we have a lot of nixos users, we'd notice (via nix
> store verifies) if the corruption was more widespread. We believe it
> only triggers with QEMU's snapshots mode (but don't quote me on that).

I have had this with 6.10.6 #1-NixOS (with nocow_lock patch added) _on 
bare hardware_, no qemu involved.

So far, i have seen it only on files in /var/lib/nixos, similar to 
https://github.com/NixOS/nixpkgs/issues/126971.

nix-store --verify --check-contents is still running, but no errors yet.

Also, copygc and rebalance block suspends for me, though the fs gets 
unmounted fine on shutdown.

Mount options:
> /dev/nvme0n1p2:/dev/sdc3:/dev/sdd2:/dev/sde3:/dev/sdb3:/dev/sda3 on / type bcachefs (rw,relatime,metadata_replicas=2,data_replicas=2,background_compression=zstd,metadata_target=ssd,foreground_target=ssd.tlc,background_target=hdd,promote_target=ssd)



      parent reply	other threads:[~2024-08-27  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  3:29 Kent Overstreet
2024-08-27  3:36 ` Matthew Wilcox
2024-08-27  3:40   ` Kent Overstreet
2024-08-27  3:46     ` Kent Overstreet
2024-08-27  7:57 ` clonejo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=706de714-9293-4d8c-b2bf-f91b87adc313@shakik.de \
    --to=clonejo@shakik.de \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox