From: Andrew McGlashan <andrew.mcglashan@affinityvision.com.au>
To: "Marc MERLIN" <marc@merlins.org>, Torbjørn <lists@skagestad.org>
Cc: Chris Mason <clm@fb.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: 3.15-rc6 - btrfs-transacti:4157 blocked for more than 120 seconds.
Date: Mon, 02 Jun 2014 13:55:12 +1000 [thread overview]
Message-ID: <538BF5A0.7050805@affinityvision.com.au> (raw)
In-Reply-To: <20140601212926.GH22161@merlins.org>
Hi,
I'm getting "blocked for more than 120 seconds" messages too.
In my case, it is for a simple RAID1 volume that is rebuilding for the
first time (new volume), whilst mounted as a LUKS crypt volume and
writing /dev/zero before actual deployment.
I am running a stock Wheezy kernel:
~ # uname -a
Linux n4800eco-a 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3 x86_64 GNU/Linux
As I am deliberately NOT running btrfs, the common link may be mdadm or
LUKS.
I'm also noticing btrfs modules being loaded on another box, even though
I am not at all ready to trust btrfs for any file system at this time.
There may be some bug with mdadm/crypt(LUKS)/btrfs -- or it may have
nothing to do with btrfs. My problem almost certainly isn't btrfs
unless there is some kernel code giving me grief without loading the
btrfs module.
More details of my problem:
https://lists.debian.org/debian-user/2014/06/msg00070.html
NB: working through my problem in a dropbear busybox environment that
hasn't loaded btrfs module. The kernel is the same as the /normal/
system, compliments of mkinitramfs tool....
Cheers
A.
next prev parent reply other threads:[~2014-06-02 4:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 18:11 3.15-rc6 - btrfs-transacti:4157 blocked for more than 120 seconds Torbjørn
2014-05-27 19:09 ` Chris Mason
[not found] ` <5384F0B4.7040309@skagestad.org>
2014-05-27 20:42 ` Torbjørn
2014-05-27 20:50 ` Chris Mason
2014-05-27 21:15 ` Chris Mason
2014-05-28 5:53 ` Torbjørn
2014-05-28 13:41 ` Chris Mason
2014-05-28 14:56 ` Torbjørn
2014-06-01 21:29 ` Marc MERLIN
2014-06-02 3:55 ` Andrew McGlashan [this message]
2014-06-02 7:29 ` Torbjørn
2014-06-05 11:44 ` Gary Coulbourne
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=538BF5A0.7050805@affinityvision.com.au \
--to=andrew.mcglashan@affinityvision.com.au \
--cc=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@skagestad.org \
--cc=marc@merlins.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).