From: Theodore Ts'o <tytso@mit.edu>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: ext4: WARNING: CPU: 10 PID: 23340 at fs/block_dev.c
Date: Thu, 9 Apr 2015 16:27:36 -0400 [thread overview]
Message-ID: <20150409202736.GA13705@thunk.org> (raw)
In-Reply-To: <55269891.3050709@oracle.com>
On Thu, Apr 09, 2015 at 11:19:45AM -0400, Sasha Levin wrote:
>
> Nope, I just got new servers to play with and decided to try xfstests.
>
> I can try bisection if it doesn't sound familiar, but since it's metal
> servers it'll take a while.
It's in the "dangerous" group, which may very well mean that it's
known to cause systems to crash. In general I tend to run either
"check -g quick" as a smoke test, or "check -g auto" with a variety of
different ext4 configurations. The former takes about 30 minuts, and
the latter (given my current list of test configs) takes a bit under
24 hours.
I tried manually running generic/019, and even though I have
CONFIG_FAIL_MAKE_REQUEST defined, /sys/kernel/debug/fail_make_request
isn't present, and so the test complains that I haven't compiled it
into my kernel --- even though /proc/config.gz confirms that it is
enabled.
Is there anything special I have to do to get generic/019 to run?
Thanks,
- Ted
P.S. I have provided for ext4 developers are preconfigured kvm test
image that makes it very easy to do tests without needing to use bare
metal; let me know if you're interested in getting a quick start to
our setup.
next prev parent reply other threads:[~2015-04-09 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 14:14 ext4: WARNING: CPU: 10 PID: 23340 at fs/block_dev.c Sasha Levin
2015-04-09 15:17 ` Theodore Ts'o
2015-04-09 15:19 ` Sasha Levin
2015-04-09 20:27 ` Theodore Ts'o [this message]
2015-04-09 20:49 ` Sasha Levin
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=20150409202736.GA13705@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.