From: Theodore Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Eric Sandeen <sandeen@redhat.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
Ext4 Mailing List <linux-ext4@vger.kernel.org>,
Linux FS Maling List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Maling List <linux-kernel@vger.kernel.org>
Subject: Re: ext4 blocks up
Date: Mon, 2 Jul 2012 14:14:42 -0400 [thread overview]
Message-ID: <20120702181442.GC5795@thunk.org> (raw)
In-Reply-To: <20120702175341.GN6679@quack.suse.cz>
On Mon, Jul 02, 2012 at 07:53:41PM +0200, Jan Kara wrote:
>
> > Can you send me a pointer to your patches? Is this something that Al
> http://www.spinics.net/lists/kernel/msg1355763.html
Ah, right. OK, I didn't realize until I took a closer look that
xfstests #68 was testing file system freezes while running fsstress.
So Artem, what I'd suggest doing for now is to simply comment out test
#68 from your xfstests's group file and just avoid running that test
until this gets sorted. I simply hadn't noticed since for most of my
quick checks I tend to use -g quick, and -g auto more rarely (i.e.,
before I push changes to Linus, and every so often during the dev
cycle), and test #68 isn't run for -g quick, and it's only failing
about 5-10% of the time in my test configuration.
- Ted
next prev parent reply other threads:[~2012-07-02 18:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 12:15 ext4 blocks up Artem Bityutskiy
2012-07-02 14:44 ` Theodore Ts'o
2012-07-02 14:54 ` Artem Bityutskiy
2012-07-02 15:14 ` Theodore Ts'o
2012-07-02 15:20 ` Theodore Ts'o
2012-07-02 16:45 ` Theodore Ts'o
2012-07-02 16:54 ` Eric Sandeen
2012-07-02 17:31 ` Jan Kara
2012-07-02 17:43 ` Theodore Ts'o
2012-07-02 17:53 ` Jan Kara
2012-07-02 18:14 ` Theodore Ts'o [this message]
2012-07-02 16:55 ` Artem Bityutskiy
2012-07-02 16:54 ` Artem Bityutskiy
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=20120702181442.GC5795@thunk.org \
--to=tytso@mit.edu \
--cc=dedekind1@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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.