linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 73051] Hung Tasks related to ext4 IO
Date: Tue, 08 Apr 2014 11:20:36 +0000	[thread overview]
Message-ID: <bug-73051-13602-BpSoVMq9i4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-73051-13602@https.bugzilla.kernel.org/>

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

--- Comment #3 from Nik Martin <nik.martin@gmail.com> ---
I can try that, and see if I can replicate the issue. I'm not exactly sure
how to disable bcache, it's not the most well documented system.
On Apr 7, 2014 8:25 AM, <bugzilla-daemon@bugzilla.kernel.org> wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=73051
>
> Jan Kara <jack@suse.cz> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|NEW                         |NEEDINFO
>                  CC|                            |jack@suse.cz
>
> --- Comment #2 from Jan Kara <jack@suse.cz> ---
> Looking into the traces, this doesn't seem to be ext4 problem at the first
> sight. We are waiting in filemap_fdatawait_range() for IO on the page to
> finish. It seems that never happens which would be a bug somewhere in the
> block
> layer, device mapper, etc. Seeing that you mention bcache, would it be
> possible
> to try whether the hangs happen without it?
>
> --
> You are receiving this mail because:
> You reported the bug.
>

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

      parent reply	other threads:[~2014-04-08 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 20:26 [Bug 73051] New: Hung Tasks possibly related to ext4 IO bugzilla-daemon
2014-04-04 16:23 ` [Bug 73051] Hung Tasks " bugzilla-daemon
2014-04-04 16:24 ` bugzilla-daemon
2014-04-07 13:24 ` bugzilla-daemon
2014-04-08 11:20 ` bugzilla-daemon [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=bug-73051-13602-BpSoVMq9i4@https.bugzilla.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 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).