From: "Theodore Ts'o" <tytso@mit.edu>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: linux-btrfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: Is generic/647 known failing test for btrfs?
Date: Sat, 23 Oct 2021 22:29:05 -0400 [thread overview]
Message-ID: <YXTE8bHlL3zEBrW0@mit.edu> (raw)
In-Reply-To: <20211024091701.8ED1.409509F4@e16-tech.com>
On Sun, Oct 24, 2021 at 09:17:02AM +0800, Wang Yugui wrote:
> Hi,
>
> Yes. It is a known problem of btrfs and others.
Hmmm, I haven't noticed a problem running generic/647 on ext4, xfs,
f2fs, reiserfs, overlayfs, and vfat. I do see the proposed iomap
changes referenced in [1] which is a prereqsuite for [2]. but it
appears that most other file systems (both thoes that do and don't use
iomap) are able to pass generic/647 even without the iomap changes
proposed in [1].
[1] https://lore.kernel.org/all/20210827164926.1726765-1-agruenba@redhat.com/
[2] https://lore.kernel.org/linux-btrfs/20211023115852.2517.409509F4@e16-tech.com/T/
- Ted
prev parent reply other threads:[~2021-10-24 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-23 15:34 Is generic/647 known failing test for btrfs? Theodore Ts'o
2021-10-24 1:17 ` Wang Yugui
2021-10-24 2:29 ` Theodore Ts'o [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=YXTE8bHlL3zEBrW0@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangyugui@e16-tech.com \
/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