From: "Theodore Ts'o" <tytso@mit.edu>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: 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 10:44:44 -0400 [thread overview]
Message-ID: <20120702144444.GA18074@thunk.org> (raw)
In-Reply-To: <1341231316.2979.11.camel@sauron.fi.intel.com>
On Mon, Jul 02, 2012 at 03:15:16PM +0300, Artem Bityutskiy wrote:
> Hi Ted,
>
> first of all I want to remind you about the sync_supers changes which
> you said you'd make sure get properly reviewed and tested for v3.5. But
> I am getting worried about missing also 3.5.
>
> I wanted to re-send the patch-set, but I cannot test it because ext4
> blocks when I test it with xfstests.
Sorry, I've just been totally swamped this past couple of monthes;
work deadlines, plus a lot of other things that have been just keeping
me totally overloaded.
Can you tell me *which* xfstest this was blocking on? I generally run
xfstests under KVM, on the console, which is nice because the xfstests
output gets interleaved with any kernel oops/softlock up messages.
Also, for the sort of changes you are doing using the check -g quick
is probably good enough, that will get you unblocked.
I don't recall anything going wrong with a -g auto run with a standard
4k block size, but I'll give it a try on my end and see what I get.
- Ted
next prev parent reply other threads:[~2012-07-02 14:44 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 [this message]
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
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=20120702144444.GA18074@thunk.org \
--to=tytso@mit.edu \
--cc=dedekind1@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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.