All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Metadata corruption detected at xfs_inode_buf_verify
Date: Wed, 5 Apr 2017 17:36:13 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.21.1.1704051729340.1086@trent.utfs.org> (raw)

Hi,

I have a raspberrypi and try to use that as a small file server. After
trying to delete a ~1TB direcory, it locked up and was then power cycled. 
Now I cannot mount the XFS partition any more:

===============================================
$ mount -t xfs /dev/mapper/owc1 /mnt/disk
mount: mount /dev/mapper/owc1 on /mnt/disk failed: Structure needs cleaning

   [producing lots of messages in dmesg, see below]


$ xfs_repair -v /dev/mapper/owc1
Phase 1 - find and verify superblock...
        - reporting progress in intervals of 15 minutes
        - block cache size set to 26024 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 3455547 tail block 3450129
ERROR: The filesystem has valuable metadata changes in a log which needs 
[...]
===============================================

Mounting with -o ro,norecovery works, and the directory I wanted to remove 
is still there, in parts - only about 200 GB have been deleted.

Full script log and .config: http://nerdbynature.de/bits/4.11.0-rc5/xfs/

Any ideas on how to solve this?

Thanks,
Christian.
-- 
BOFH excuse #431:

Borg implants are failing

             reply	other threads:[~2017-04-06  0:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  0:36 Christian Kujau [this message]
2017-04-06  8:08 ` Metadata corruption detected at xfs_inode_buf_verify Carlos Maiolino
2017-04-06 17:50   ` Christian Kujau
2017-07-16 18:01 Christian Kujau
2017-07-17  7:47 ` Christian Kujau
2017-07-17 17:48   ` Brian Foster
2017-07-17 18:44     ` Christian Kujau
2017-07-19  6:54   ` Christoph Hellwig

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=alpine.DEB.2.21.1.1704051729340.1086@trent.utfs.org \
    --to=lists@nerdbynature.de \
    --cc=linux-xfs@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.