From: Theodore Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: remove unaligned AIO warning printk
Date: Tue, 25 Dec 2012 13:34:27 -0500 [thread overview]
Message-ID: <20121225183427.GC5318@thunk.org> (raw)
In-Reply-To: <50AD09F0.6090706@redhat.com>
On Wed, Nov 21, 2012 at 11:05:52AM -0600, Eric Sandeen wrote:
> Although I put this in, I now think it was a bad decision.
> For most users, there is very little to be done in this case. They
> get the message, once per day, with no real context or proposed action.
> TBH, it generates support calls when it probably does not need to;
> the message sounds more dire than the situation really is.
>
> Just nuke it. Normal investigation via blktrace or whatnot can
> reveal poor IO patterns if bad performance is encountered.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Thanks, applied.
- Ted
prev parent reply other threads:[~2012-12-25 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 17:05 [PATCH] ext4: remove unaligned AIO warning printk Eric Sandeen
2012-11-21 19:47 ` Theodore Ts'o
2012-11-21 20:03 ` Eric Sandeen
2012-12-25 18:34 ` 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=20121225183427.GC5318@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).