From: Dave Chinner <david@fromorbit.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] btrfs: test log replay after fsync of file with prealloc extents beyond eof
Date: Wed, 23 Feb 2022 10:44:32 +1100 [thread overview]
Message-ID: <20220222234432.GF3061737@dread.disaster.area> (raw)
In-Reply-To: <abbc821350c8ef515e0a0317b5cbd64e3c5b81ab.1645099449.git.fdmanana@suse.com>
On Thu, Feb 17, 2022 at 12:14:21PM +0000, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Test that after a full fsync of a file with preallocated extents beyond
> the file's size, if a power failure happens, the preallocated extents
> still exist after we mount the filesystem.
>
> This test currently fails and there is a patch for btrfs that fixes this
> issue and has the following subject:
>
> "btrfs: fix lost prealloc extents beyond eof after full fsync"
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
> ---
> tests/btrfs/261 | 79 +++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/261.out | 10 ++++++
What is btrfs specific about this test?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2022-02-22 23:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 12:14 [PATCH] btrfs: test log replay after fsync of file with prealloc extents beyond eof fdmanana
2022-02-22 23:44 ` Dave Chinner [this message]
2022-02-23 12:12 ` Filipe Manana
2022-02-24 2:21 ` Dave Chinner
2022-03-02 11:33 ` Filipe Manana
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=20220222234432.GF3061737@dread.disaster.area \
--to=david@fromorbit.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