From: Xavier Bassery <xavier@bartica.org>
To: david pu <pulq.ustc@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: task btrfs-transacti:1076 blocked for more than 120 seconds
Date: Mon, 21 Oct 2013 12:37:31 +0200 [thread overview]
Message-ID: <20131021123731.4ea7a23e@renoir.lan> (raw)
In-Reply-To: <CA+yNr1dyhC1=Rv=wuzV-YzSdEOmEEB=OLo=SJwmSMvsvhmmZ-g@mail.gmail.com>
On Mon, 21 Oct 2013 16:36:41 +0800
david pu <pulq.ustc@gmail.com> wrote:
> hello,
> I'm running into btrfs-transaction hang issue with below call trace
> from dmesg[1].
> when this issue happens, all filesystem r/w access will be blocked and
> no response in terminal. I'm using Ubuntu raring(linux 3.2 kernel)
> 64bit kernel as below:
> Linux dpu-e6410 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC
> 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> is it a known issue? How to recover from such task hung status?
Hi David,
a simple btrfs user reply here.
I don't know if this will solve your issue at hand, but when using
btrfs it is strongly advised to run a much more recent kernel than 3.2
as found in Ubuntu precise (12.4).
The reason is that they were plenty of bug fixes related to btrfs that
you would miss by sticking to an old kernel.
Could you please try the latest 3.11 (or 3.10) kernel available?
If this doesn't fix your issue, please report back so that we can
investigate further.
Regards,
Xavier
next prev parent reply other threads:[~2013-10-21 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 8:36 task btrfs-transacti:1076 blocked for more than 120 seconds david pu
2013-10-21 10:37 ` Xavier Bassery [this message]
2013-10-21 12:37 ` David Sterba
2013-10-21 15:01 ` david pu
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=20131021123731.4ea7a23e@renoir.lan \
--to=xavier@bartica.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=pulq.ustc@gmail.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).