From: Nikolay Borisov <nborisov@suse.com>
To: fdmanana@kernel.org, fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: test fstrim after doing a device replace
Date: Thu, 24 Sep 2020 11:32:52 +0300 [thread overview]
Message-ID: <4e77797e-3d0a-b90b-6ea8-ae2880a10d9b@suse.com> (raw)
In-Reply-To: <a8f27095c014466444a70b77810ba826df68e623.1600870988.git.fdmanana@suse.com>
On 23.09.20 г. 17:31 ч., fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Test that after replacing a device, if we run fstrim against the filesystem
> we do not trim/discard allocated chunks in the new device. We verify that
> allocated chunks in the new device were not trim/discarded by mounting the
> new device only in degraded mode, as this is the easiest way to verify it.
>
> This currently fails on btrfs (since kernel 5.2) and is fixed by a patch
> that has the following subject:
>
> "btrfs: fix filesystem corruption after a device replace"
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
prev parent reply other threads:[~2020-09-24 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 14:31 [PATCH] btrfs: test fstrim after doing a device replace fdmanana
2020-09-24 8:32 ` Nikolay Borisov [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=4e77797e-3d0a-b90b-6ea8-ae2880a10d9b@suse.com \
--to=nborisov@suse.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).