From: Theodore Ts'o <tytso@mit.edu>
To: Eryu Guan <guaneryu@gmail.com>
Cc: Eryu Guan <eguan@redhat.com>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel
Date: Wed, 1 Jun 2016 09:53:21 -0400 [thread overview]
Message-ID: <20160601135321.GD5357@thunk.org> (raw)
In-Reply-To: <20160601063822.GH10350@eguan.usersys.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 372 bytes --]
On Wed, Jun 01, 2016 at 02:38:22PM +0800, Eryu Guan wrote:
> I think I can try configs from other venders such as SuSE, Ubuntu. If
> you can share your config file I'll test it as well.
Here are the configs I'm using. The 32-bit config is used with KVM.
The 64-bit config is used with KVM and Google Compute Engine
(http://thunk.org/gce-xfstests).
Cheers,
- Ted
[-- Attachment #2: ext4-32.config.bz2 --]
[-- Type: application/octet-stream, Size: 20370 bytes --]
[-- Attachment #3: ext4-64.config.bz2 --]
[-- Type: application/octet-stream, Size: 13625 bytes --]
next prev parent reply other threads:[~2016-06-01 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 14:09 xfstests generic/130 hang with non-4k block size ext4 on 4.7-rc1 kernel Eryu Guan
2016-05-31 15:40 ` Theodore Ts'o
2016-06-01 6:38 ` Eryu Guan
2016-06-01 13:53 ` Theodore Ts'o [this message]
2016-06-01 16:58 ` Eryu Guan
2016-06-02 8:58 ` Jan Kara
2016-06-02 12:17 ` Jan Kara
2016-06-02 12:30 ` Nikola Pajkovsky
2016-06-03 10:16 ` Eryu Guan
2016-06-03 11:58 ` Jan Kara
2016-06-08 12:56 ` Jan Kara
2016-06-08 14:23 ` Holger Hoffstätte
2016-06-09 7:23 ` Nikola Pajkovsky
2016-06-09 15:04 ` Jan Kara
2016-06-10 5:52 ` Nikola Pajkovsky
2016-06-16 13:26 ` Jan Kara
2016-06-16 14:42 ` Nikola Pajkovsky
2016-06-20 11:39 ` Jan Kara
2016-06-20 12:59 ` Nikola Pajkovsky
2016-06-21 10:11 ` Jan Kara
2016-06-22 8:55 ` Nikola Pajkovsky
2016-06-09 14:59 ` Jan Kara
2016-06-10 8:37 ` Eryu Guan
2016-06-12 3:28 ` Eryu Guan
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=20160601135321.GD5357@thunk.org \
--to=tytso@mit.edu \
--cc=eguan@redhat.com \
--cc=guaneryu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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 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.