linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: "'linux-xfs@vger.kernel.org'" <linux-xfs@vger.kernel.org>
Subject: Weird xfs_repair error
Date: Thu, 6 Jul 2017 15:30:20 +0200	[thread overview]
Message-ID: <20170706153020.0ad6dd47@harpe.intellique.com> (raw)

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


After a RAID controller went bananas, I encountered an XFS corruption
on a filesystem. Weirdly, the corruption seems to be mostly located in
lost+found.

(I'm currently working on a metadump'd image of course, not the real
thing; there are 90TB of data to be hopefully salvaged in there).

"ls /mnt/rescue/lost+found" gave this:

XFS (loop0): metadata I/O error: block 0x22b03f490
("xfs_trans_read_buf_map") error 117 numblks 16 
XFS (loop0): xfs_imap_to_bp: xfs_trans_read_buf() returned error 117.
XFS (loop0): Corruption detected. Unmount and run xfs_repair 
XFS (loop0): Corruption detected. Unmount and run xfs_repair

I've run xfs_repair 4.9 on the xfs_mdrestored image. It dumps an insane
lot of errors (the output log is 65MB)  and ends with this very strange
message:

disconnected inode 26417467, moving to lost+found
disconnected inode 26417468, moving to lost+found
disconnected inode 26417469, moving to lost+found
disconnected inode 26417470, moving to lost+found

fatal error -- name create failed in lost+found (117), filesystem may
be out of space

Even stranger, after mounting back the image, there is no lost+found
anywhere to be found! However the filesystem has lots of free space and
free inodes, how come?

df -i
Sys. fich.                    Inodes  IUtil.     ILibre IUti% Monté sur
rootfs                             0       0          0     - /
/dev/root                          0       0          0     - /
tmpfs                        2058692     990    2057702    1% /run
tmpfs                        2058692       6    2058686    1% /run/lock
tmpfs                        2058692    1623    2057069    1% /dev
tmpfs                        2058692       3    2058689    1% /run/shm
guitare:/mnt/raid/partage   33554432  305069   33249363    1% /mnt/qnap1
/dev/loop0                4914413568 5199932 4909213636    1% /mnt/rescue

df
/dev/loop0                122858252288 88827890868 34030361420  73% /mnt/rescue

I'll give a shot to a newer version of xfs_repair just in case...

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

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

             reply	other threads:[~2017-07-06 13:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 13:30 Emmanuel Florac [this message]
2017-07-06 13:48 ` Weird xfs_repair error Brian Foster
2017-07-06 14:49   ` Emmanuel Florac
2017-07-06 23:28 ` Dave Chinner
2017-07-07 11:36   ` Emmanuel Florac
2017-07-07 11:50   ` Emmanuel Florac
2017-07-07 15:36     ` Darrick J. Wong
2017-07-10 17:29       ` Emmanuel Florac
2017-07-11 13:23       ` Emmanuel Florac
2017-07-17 17:11         ` Brian Foster
2017-07-24 14:27           ` Emmanuel Florac
2017-07-24 14:51             ` Brian Foster
2017-07-25 16:44               ` Emmanuel Florac
2017-07-25 17:16               ` Emmanuel Florac
2017-07-25 19:22                 ` Brian Foster

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=20170706153020.0ad6dd47@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --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 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).