From: Chris Mason <chris.mason@oracle.com>
To: Cheng Shao <zchshao@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: writes got stuck
Date: Tue, 19 Apr 2011 08:06:13 -0400 [thread overview]
Message-ID: <1303214712-sup-9341@think> (raw)
In-Reply-To: <BANLkTinJt3n69=NpPKAvFd3LPeDGnn0bkA@mail.gmail.com>
Excerpts from Cheng Shao's message of 2011-04-18 17:49:29 -0400:
> Hi there,
>
> I'm periodically having issues with btrfs running in a Ubuntu VM using
> VirtualBox. After the VM has been running for a while (a couple days),
> any write operation seems getting stuck. The read seems totally fine.
> I tried a simple dd of a 4M file and it got stuck after writing 131K
> worth of data.
>
> I don't know if this is btrfs related, or it is due to some bug in
> VritualBox. Could you guys provide information on how to debug this
> (collecting logs, getting dumps etc.)? Thanks a lot!
Which kernel are you running?
Definitely look for kernel messages (run dmesg etc). If there are no
crashes or related messages you can run sysrq-t and send the output and
we can look for the deadlock.
-chris
next prev parent reply other threads:[~2011-04-19 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 21:49 writes got stuck Cheng Shao
2011-04-19 12:06 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-25 5:28 Chris Murphy
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=1303214712-sup-9341@think \
--to=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=zchshao@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).