linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Lakin <kennethlakin@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: 4.1.6 gentoo-hardened: Hang during rename
Date: Sat, 29 Aug 2015 13:23:57 -0700	[thread overview]
Message-ID: <55E214DD.9070504@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Hey. It looks like I'm being bitten by:
http://article.gmane.org/gmane.comp.file-systems.btrfs/44987/ except I'm
hitting it during rename, rather than unlink. Dmesg spew here:
http://pastebin.ca/3137198 (That pastebin post includes the -unrelated-
source of the W taint.)

I'm running on Gentoo hardened-sources 4.1.6 on x86 (rather than amd64).
The affected volume is mounted with
"rw,relatime,ssd,discard,space_cache,autodefrag" and -AFAIK- has no
subvolumes.

emerge is the blocked program and is the Gentoo package manager. This
lockup happens occasionally during the "Updating Portage cache" step of
the emerge sync operation. The emerge task is unkillable and is blocked
in D status. Attempts to re-run the cache update task have it hang at
what appears to be the same place. Only a reboot can "fix" the problem.
The rest of the system works just fine; the only thing that appears to
be blocked is the Portage cache update.

I couldn't find an open bug for this, but my Google-fu may be weak
today. Did I miss the bug report, or is this a currently unknown or
unconfirmed issue? Let me know if I can help with diagnostics.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-08-29 20:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-29 20:23 Kenneth Lakin [this message]
2015-08-29 20:57 ` 4.1.6 gentoo-hardened: Hang during rename Kenneth Lakin
2015-08-30 10:10 ` Filipe David Manana

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=55E214DD.9070504@gmail.com \
    --to=kennethlakin@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 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).