All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 20902] High IO wait when writing to ext4
Date: Fri, 29 Oct 2010 21:13:54 GMT	[thread overview]
Message-ID: <201010292113.o9TLDsI0020719@demeter1.kernel.org> (raw)
In-Reply-To: <bug-20902-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=20902


Theodore Tso <tytso@mit.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tytso@mit.edu




--- Comment #11 from Theodore Tso <tytso@mit.edu>  2010-10-29 21:13:50 ---
Did things work OK with an earlier kernel version?   Is this something that has
always troubled you, or is it something which recently started when you
upgraded to the 2.6.36 kernel?

Once things are OK after "the first write", are they OK forever after that?  If
the problem re-occurs after the first write, can you say something about when
that might be?

How about replicating it on a USB attached disk?  Can you try a couple of
different scenarios with a USB attached disk?  Say,

1) With a USB attached disk using a MBR-partitioned disk?
2) With a USB attached disk set up using LVM with a single LVM volume?
3) With a USB attached disk set up using LVM and a LUKS-encrypted volume?

etc.

And can you specified what mount options, if any, that you were using?

Thanks,

-- Ted

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-10-29 21:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  8:56 [Bug 20902] New: High bugzilla-daemon
2010-10-22  8:56 ` [Bug 20902] High bugzilla-daemon
2010-10-22  8:57 ` bugzilla-daemon
2010-10-22  8:57 ` bugzilla-daemon
2010-10-22  8:58 ` bugzilla-daemon
2010-10-22  8:59 ` bugzilla-daemon
2010-10-22  9:08 ` bugzilla-daemon
2010-10-22  9:18 ` [Bug 20902] High IO wait when writing to ext4 bugzilla-daemon
2010-10-22 21:52 ` bugzilla-daemon
2010-10-22 21:54 ` bugzilla-daemon
2010-10-22 21:55 ` bugzilla-daemon
2010-10-29 16:11 ` bugzilla-daemon
2010-10-29 16:23 ` bugzilla-daemon
2010-10-29 18:08 ` bugzilla-daemon
2010-10-29 21:13 ` bugzilla-daemon [this message]
2010-10-29 21:46 ` bugzilla-daemon
2010-11-04 17:59 ` bugzilla-daemon
2010-11-04 18:46 ` bugzilla-daemon
2010-11-04 18:52 ` bugzilla-daemon
2010-11-24  3:14 ` bugzilla-daemon
2010-11-24  5:13 ` bugzilla-daemon
2010-11-24 18:41 ` bugzilla-daemon
2010-11-25  9:17 ` bugzilla-daemon
2010-11-25 15:30 ` bugzilla-daemon
2013-12-10 22:21 ` bugzilla-daemon

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=201010292113.o9TLDsI0020719@demeter1.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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.