From: Liu Bo <bo.li.liu@oracle.com>
To: Kenny MacDermid <kenny.macdermid@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs issues in 3.14
Date: Wed, 7 May 2014 10:22:46 +0800 [thread overview]
Message-ID: <20140507022245.GA15783@localhost.localdomain> (raw)
In-Reply-To: <CAEVbaUdcCQCWhZ-ZdBr_Dkv-WaMbtBkQ0n8HRfc0p9F0xw1+0A@mail.gmail.com>
On Tue, May 06, 2014 at 08:49:04PM -0300, Kenny MacDermid wrote:
> Hello,
>
> I've been having a number of issues with processes hanging due to
> btrfs using 3.14 kernels. This seems pretty new as it has been working
> fine before. I also rebuilt the filesystem and am still receiving
> hangs.
>
> The filesystem is running on dmcrypt which is running on lvm2 which is
> running on an SSD (SAMSUNG MZMTD256HAGM-000L1).
>
> When the issue occurs the process is unable to be killed and the
> system will not fully shutdown.
>
> $ uname -a
> Linux orange 3.14.2-1-ARCH #1 SMP PREEMPT Sun Apr 27 11:28:44 CEST
> 2014 x86_64 GNU/Linux
>
> $ btrfs --version
> Btrfs v3.14.1
>
> $ btrfs fi show
> Btrfs v3.14.1
>
> $ btrfs fi df /home
> Data, single: total=71.01GiB, used=68.72GiB
> System, DUP: total=8.00MiB, used=16.00KiB
> System, single: total=4.00MiB, used=0.00
> Metadata, DUP: total=1.50GiB, used=863.33MiB
> Metadata, single: total=8.00MiB, used=0.00
>
> I opened bugs 75181 and 75191 and I'll include the relevant journalctl
> entries. The kernel was upgraded from 3.14.1-1 to 3.14.2-1 during this
> time, and the filesystem was rebuilt after the orphan issue.
>
> I'm not on this list so please CC me on replies.
What does sysrq+w say when the hang happens?
-liubo
next prev parent reply other threads:[~2014-05-07 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 23:49 btrfs issues in 3.14 Kenny MacDermid
2014-05-07 2:22 ` Liu Bo [this message]
2014-05-07 12:35 ` Kenny MacDermid
2014-05-07 13:13 ` Kenny MacDermid
2014-05-08 2:48 ` Liu Bo
2014-05-08 13:51 ` Kenny MacDermid
2014-05-09 10:54 ` Liu Bo
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=20140507022245.GA15783@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=kenny.macdermid@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.