From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: task sync:2450 blocked for more than 120 seconds.
Date: Thu, 1 May 2014 17:16:06 +0000 (UTC) [thread overview]
Message-ID: <pan$5efeb$21e4ebfc$652f5a00$7fae9e71@cox.net> (raw)
In-Reply-To: ljsvpb$cl6$1@ger.gmane.org
Neuer User posted on Thu, 01 May 2014 10:14:35 +0200 as excerpted:
> It's probably best to copy al my data to another disk, then delete the
> parttiion and make a new ext4 partition. btrfs is probably still too
> experimental, I guess.
I thought I replied to this one but it was to a different, similar
problem, post.
The blocked task bug isn't entirely uncommon, and is apparently a number
of bugs with similar symptoms. One thing the devs have been requesting
on such reports is the output from a sysrq-w, which dumps the blocked
tasks so the devs can trace where the blocks are happening and fix the
bugs. Either alt-sysrq-w, if you're running direct on hardware, or
echo w > /proc/sysrq-trigger, which should work in VMs, etc, as well.
But you're correct, tracking down and fixing all these bugs is likely to
take awhile, and if you simply want something that works and don't have
the luxury of testing and waiting for fixes, switching back to ext4 or
whatever, until btrfs has matured a bit longer, would be the recommended
course of action.
And one more comment, a hint for next time. On mailing lists it's common
to quote what you're replying to and reply below it. Top posting the
reply works for that post, but messes things up for others trying to
reply to the thread as well and for later readers, since now there's
either a mixture of top-posted and in-context-posted replies at multiple
levels or people end up omitting entirely the second level and deeper
quotes that might have put the whole thing in context. Either case makes
the thread difficult to follow or to properly reply to. =:^(
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-05-01 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 6:37 task sync:2450 blocked for more than 120 seconds Neuer User
2014-05-01 8:14 ` Neuer User
2014-05-01 17:16 ` Duncan [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='pan$5efeb$21e4ebfc$652f5a00$7fae9e71@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).