From: "Theodore Ts'o" <tytso@mit.edu>
To: Li Zhijian <zhijianx.li@intel.com>
Cc: fstests@vger.kernel.org, "Li, Philip" <philip.li@intel.com>
Subject: Re: generic/388 is failed under ext4
Date: Thu, 21 Dec 2017 10:39:18 -0500 [thread overview]
Message-ID: <20171221153917.GA27177@thunk.org> (raw)
In-Reply-To: <be7e6d14-dcc9-1822-e005-4e779fc97873@intel.com>
On Thu, Dec 21, 2017 at 10:38:47AM +0800, Li Zhijian wrote:
> Hi all
>
> I'm not sure whether the failure is expected or not when i ran generic/388 under ext4
>
> i ran it from v4.11 to v4.15-rc3, they all failed.
Yes, it's a known problem, and it's on my todo list to investigate and
fix.
The use of this at $WORK is without journalling, and we don't care
about the inconsistent file system for that particular use case. (In
fact, in this particular case the iSCSI device is *gone*, and we're
using the shutdown to avoid processes to hang for a Very Long Time
after the device goes poof. At least we're no longer crashing in the
writeback functions in a block device disappears....)
- Ted
prev parent reply other threads:[~2017-12-21 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 2:38 generic/388 is failed under ext4 Li Zhijian
2017-12-21 15:39 ` 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=20171221153917.GA27177@thunk.org \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=philip.li@intel.com \
--cc=zhijianx.li@intel.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