linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philipp Klaus Krause <pkk@spth.de>
To: linux-btrfs@vger.kernel.org
Subject: BTRFS critical (device dm-2): invalid dir item name len: 77
Date: Wed, 21 Jan 2015 12:43:01 +0100	[thread overview]
Message-ID: <54BF90C5.8060100@spth.de> (raw)

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

Hello,

I've been using btrfs on a Debian GNU/Linux system. After about 9
months, I encountered my first filesystem issue. It first appeared while
doing an rm -rf, which resulted in a

rm: cannot remove […]: Directory not empty

a du -s on the directory gives an

BTRFS critical (device dm-2): invalid dir item name len: 77

I can mv directory around (which is good so it doesn't get in my way any
more), but can't rm it.

How can I get id of it?

Philipp


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

             reply	other threads:[~2015-01-21 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 11:43 Philipp Klaus Krause [this message]
2015-01-21 12:45 ` BTRFS critical (device dm-2): invalid dir item name len: 77 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=54BF90C5.8060100@spth.de \
    --to=pkk@spth.de \
    --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).