Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.net>
To: Nigel Kukard <nkukard@LBSD.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs ontop of LVM ontop of MD RAID1 supported?
Date: Sat, 2 Mar 2024 20:47:26 +0500	[thread overview]
Message-ID: <20240302204726.6d2dcd87@nvm> (raw)
In-Reply-To: <1cfb237c-5583-44e9-8bad-d91f34e29972@LBSD.net>

On Sat, 2 Mar 2024 15:01:43 +0000
Nigel Kukard <nkukard@LBSD.net> wrote:

> I'm wondering if btrfs ontop of LVM ontop of MD RAID1 is supported?  

Should be absolutely supported.

> I've managed to reproduce with 100% accuracy severe data corruption 
> using this configuration on 6.6.19.
> 
> 2 x 1.92T NVMe's in MD RAID1 configuration
> LVM volume created ontop of the MD RAID1
> btrfs filesystem on the LV
> 
> I then write about 100-200G of data. Create a snapshot. Read/write the 
> file and get these messages...

Has the MD RAID1 finished its initial sync after creation?

Have you tried waiting until it finishes and only then do thewrites to see if
the corruption is still observed (of course that's in no way a "workaround",
just to see what might cause the bug).

Do you know any kernel versions or series where this corruption did not happen?

I assume you're not saying it appeared in 6.6.19 compared to 6.6.18.

Can you try the 6.1 series? Or maybe also 6.8?

I made a Btrfs on top of LVM on top of RAID1 myself now, but on consumer SSDs.
Copying some files to it now, to check. Would be also helpful if you can find
a precise sequence of commands which can trigger the bug, less vague than
copy some files to it and see.

-- 
With respect,
Roman

  reply	other threads:[~2024-03-02 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 15:01 btrfs ontop of LVM ontop of MD RAID1 supported? Nigel Kukard
2024-03-02 15:47 ` Roman Mamedov [this message]
2024-03-02 16:09   ` Nigel Kukard
2024-03-02 16:19   ` Roman Mamedov
2024-03-19 11:05   ` Nigel Kukard
2024-03-19 13:26     ` Nigel Kukard

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=20240302204726.6d2dcd87@nvm \
    --to=rm@romanrm.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nkukard@LBSD.net \
    /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