linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Matthew Wilcox <willy@infradead.org>
Cc: 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: Mon, 26 Aug 2024 23:46:05 -0400	[thread overview]
Message-ID: <7qttwffpydvnzqm7mjflqui7ywjb5gvhmvwebxktoth33ffpnc@llewszyqw42z> (raw)
In-Reply-To: <2iroae47robod2vijalby64iczk2emltrshmztlwyrxmkeiydd@4lxo55nlgpxo>

On Mon, Aug 26, 2024 at 11:40:57PM GMT, Kent Overstreet wrote:
> On Tue, Aug 27, 2024 at 04:36:33AM GMT, Matthew Wilcox wrote:
> > On Mon, Aug 26, 2024 at 11:29:52PM -0400, Kent Overstreet wrote:
> > > We had a report of corruption on nixos, on tests that build a system
> > > image, it bisected to the patch that enabled buffered writes without
> > > taking the inode lock:
> > > 
> > > https://evilpiepirate.org/git/bcachefs.git/commit/?id=7e64c86cdc6c
> > > 
> > > It appears that dirty folios are being dropped somehow; corrupt files,
> > > when checked against good copies, have ranges of 0s that are 4k aligned
> > > (modulo 2k, likely a misaligned partition).
> > > 
> > > 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).
> > 
> > Just to be crystal clear here, the corruption happens while running
> > bcachefs in the qemu guest, and it doesn't matter what the host
> > filesystem is?
> > 
> > Or did I misunderstand, and it occurs while running anything inside qemu
> > on top of a bcachefs host?
> 
> The host is running bcachefs, backing qemu's disk image.
> 
> (And I'm using nested virtualization for bisecting, it's been a lot to
> keep straight).

Also, the size of the missing data is not a power of two - it's not a
single folio.


  reply	other threads:[~2024-08-27  3:46 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 [this message]
2024-08-27  7:57 ` clonejo

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=7qttwffpydvnzqm7mjflqui7ywjb5gvhmvwebxktoth33ffpnc@llewszyqw42z \
    --to=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=willy@infradead.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