linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tobias <tracer@robotech.de>
To: Chris Mason <chris.mason@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: Blocked for more than 120 seconds
Date: Fri, 02 Dec 2011 14:46:48 +0100	[thread overview]
Message-ID: <4ED8D6C8.4020609@robotech.de> (raw)
In-Reply-To: <20111201184158.GB10535@shiny>

Hi Chris!

Am 01.12.2011 19:41, schrieb Chris Mason:
>
> So, the transaction close is in btrfs_evict_inode, which sounds like a
> deadlock recently fixed by this commit:
>
> http://git.kernel.org/?p=linux/kernel/git/mason/linux-btrfs.git;a=commit;h=aa38a711a893accf5b5192f3d705a120deaa81e0
>
> If you pull the for-linus branch from today, hopefully the problem will
> be gone.
>

This looks very good. With this Kernel i still have some hangs, but only 
in rsync, only under high load and they don't lock up the system - so i 
guess it's ok now.

Thank You very much for Your help!

When will this patches go into the main Kernel?

Tobias


  reply	other threads:[~2011-12-02 13:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  8:16 Blcoked for more than 120 seconds Tobias
2011-11-28  9:29 ` Chris Samuel
2011-11-30  9:44   ` Blocked " Tobias
2011-11-30 14:10     ` Chris Mason
     [not found]       ` <4ED738E5.3080200@robotech.de>
2011-12-01 18:41         ` Chris Mason
2011-12-02 13:46           ` Tobias [this message]
2011-12-02 14:01             ` Chris Mason
2011-12-04 12:11               ` Konstantinos Skarlatos
2011-12-02 15:22             ` Konstantinos Skarlatos
2011-12-02 15:48               ` Tobias
2011-12-02 19:53                 ` Konstantinos Skarlatos
2011-12-03  0:35                   ` Konstantinos Skarlatos
2011-12-03 14:36                     ` Konstantinos Skarlatos
2011-12-05 13:12                       ` Chris Mason
2011-12-25  1:06                         ` Konstantinos Skarlatos

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=4ED8D6C8.4020609@robotech.de \
    --to=tracer@robotech.de \
    --cc=chris.mason@oracle.com \
    --cc=linux-btrfs@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).