From: david pu <pulq.ustc@gmail.com>
To: dsterba@suse.cz, david pu <pulq.ustc@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: task btrfs-transacti:1076 blocked for more than 120 seconds
Date: Mon, 21 Oct 2013 23:01:14 +0800 [thread overview]
Message-ID: <CA+yNr1cRipOhvkNsf8d2sR1bm1hdL6xLicBBFyiWTd=oaQjGHw@mail.gmail.com> (raw)
In-Reply-To: <20131021123728.GJ1032@twin.jikos.cz>
On Mon, Oct 21, 2013 at 8:37 PM, David Sterba <dsterba@suse.cz> wrote:
> On Mon, Oct 21, 2013 at 04:36:41PM +0800, david pu wrote:
>> 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?
>
> The message can occur when
>
> 1) system is under heavy load or fragmentation slows down the IO, this
> is harmless, the warnings stop after a few cycles
It happens after I login into Ubuntu with lightdm.I did not find a
method to reproduce it consistently.
>
> 2) it's a bug and the system cannot move forward due to a deadlock, the
> warnings appear repeatedly and the IO seems to be stalled
>
> For a 3.2 kernel it's possible that the bug is there.
I'm very sorry about the kernel version I pasted in previous email. I
pasted wrong uname -a result. it should be:
Linux dpu-desktop 3.8.0-31-generic #46-Ubuntu SMP Tue Sep 10 20:03:44
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
will upgrade kernel to latest version to have a try.
>
> david
--
() ASCII Ribbon Campaign
/\ Keep it simple!
prev parent reply other threads:[~2013-10-21 15:01 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
2013-10-21 12:37 ` David Sterba
2013-10-21 15:01 ` david pu [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='CA+yNr1cRipOhvkNsf8d2sR1bm1hdL6xLicBBFyiWTd=oaQjGHw@mail.gmail.com' \
--to=pulq.ustc@gmail.com \
--cc=dsterba@suse.cz \
--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).