linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: remove unaligned AIO warning printk
Date: Wed, 21 Nov 2012 14:03:17 -0600	[thread overview]
Message-ID: <50AD3385.1030500@redhat.com> (raw)
In-Reply-To: <20121121194728.GA6895@thunk.org>

On 11/21/12 1:47 PM, Theodore Ts'o wrote:
> 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.
> 
> I wonder if this might be a good thing to enable or disable via sysfs
> tuning knob, just to make it a little easier for a random application
> developer to test for this?

*shrug* would be more knobs & more complexity; I bet 99% of people reporting
it would never have known the knob was there, and doubtful they'd have turned
it on.  If developers cared, they'd probably have done the proper thing in the
first place.  I guess I'm skeptical of the usefulness.

> And do you have a list of the bad applications so we can nag them to
> fix them?

Whenever we get it reported, it's some proprietary thing.  So no, not
really, I'm afraid.

But google live search thinks it's virtualbox, kvm, and java ;)

"Unaligned AIO/DIO on inode" turns up plenty.

Can you do some sort of google-grep-awk to find every app that's been
reported on lists?  ;)

-Eric

> 					- Ted
> 



  reply	other threads:[~2012-11-21 20:03 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 [this message]
2012-12-25 18:34 ` Theodore Ts'o

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=50AD3385.1030500@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).