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 21:19:23 +0500 [thread overview]
Message-ID: <20240302211923.6e4cfad4@nvm> (raw)
In-Reply-To: <20240302204726.6d2dcd87@nvm>
On Sat, 2 Mar 2024 20:47:26 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> 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.
After some file copying, snapshotting and reading back, I did not manage to
reproduce any corruption so far, on 6.6.18.
--
With respect,
Roman
next prev parent reply other threads:[~2024-03-02 16:19 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
2024-03-02 16:09 ` Nigel Kukard
2024-03-02 16:19 ` Roman Mamedov [this message]
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=20240302211923.6e4cfad4@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