From: Panagiotis Papadakos <papadako@ics.forth.gr>
To: linux-xfs@vger.kernel.org
Subject: xfs_repair: fatal error -- couldn't map inode 13199169, err = 117
Date: Wed, 01 Feb 2023 14:55:12 +0200 [thread overview]
Message-ID: <86696f1f1b39a175e99f43128f09a722@mailhost.ics.forth.gr> (raw)
Dear all,
I am using XFS on an ICY-BOX 4-bay USB RAID enclosure which
unfortunately has been corrupted (probably due to some power-down).
I have used xfs_repair -L, which after a huge number of messages about
free inode references, bad hash tables, etc, fails with the following
error:
fatal error -- couldn't map inode 13199169, err = 117
Is there anything I can do or should I consider my data lost?
xfs_repair version 6.0.0
kernel: 6.1.0-rc5
Best regards
Panagiotis, a novice XFS user
next reply other threads:[~2023-02-01 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EHyZekx1O-pqePkGfRDKAjIdo4T1Oc5ZgucxgVcs4zwc5d7uPmA6F9sPBM9gjh7xw8hXbfVfy_kg7NtvmvBU8A==@protonmail.internalid>
2023-02-01 12:55 ` Panagiotis Papadakos [this message]
2023-02-03 12:38 ` xfs_repair: fatal error -- couldn't map inode 13199169, err = 117 Carlos Maiolino
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=86696f1f1b39a175e99f43128f09a722@mailhost.ics.forth.gr \
--to=papadako@ics.forth.gr \
--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