From: Josef Bacik <josef@redhat.com>
To: Roman Mamedov <rm@romanrm.ru>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs lock-up on copying files
Date: Thu, 30 Jun 2011 10:37:51 -0400 [thread overview]
Message-ID: <4E0C8A3F.2060202@redhat.com> (raw)
In-Reply-To: <20110630123738.6042e563@natsu>
On 06/30/2011 02:37 AM, Roman Mamedov wrote:
> Hello,
>
> I was copying a set of files to a btrfs filesystem, and the copy process locked-up with the following messages in dmesg.
>
> The kernel version is 2.6.39.1; the filesystem was recently resized from 3 to 4TB (if that matters).
>
> It is mounted remotely via AoE but the remote host is up and no errors regarding block devices are registered on it.
> The network is fine and the AoE device with btrfs continues to be accessible normally on the client.
>
Can you do sysrq+w when this happens? The caching kthread should still
be able to make progress, which is what we seem to be waiting on. Does
it eventually unhang and continue on? Thanks,
Josef
next prev parent reply other threads:[~2011-06-30 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 6:37 btrfs lock-up on copying files Roman Mamedov
2011-06-30 14:37 ` Josef Bacik [this message]
2011-06-30 14:43 ` Roman Mamedov
2011-06-30 14:52 ` Josef Bacik
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=4E0C8A3F.2060202@redhat.com \
--to=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=rm@romanrm.ru \
/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).