From: "Péter András Felvégi" <petschy@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: My XFS volume died, please help!
Date: Sat, 3 Jun 2017 01:21:31 +0200 [thread overview]
Message-ID: <CAG3eYYQMTdmCK9EdJA4hfYSSPStLSC=YBK+tvk67r6Vn4-UcxQ@mail.gmail.com> (raw)
Hello,
after a power outage, the mount replayed the journal and no errors
were reported, but the mounted XFS volume had suspiciously little free
space. So I unmounted, and ran xfs_repair which crashed in phase 5
with a floating point exception. After that I was unable to mount
again, due to metadata corruption, so the repair made things worse.
Please help!
Linux 4.4.66 x86_64, Debian Jessie, xfsprogs 3.2.1
xps_repair output:
Phase 5 - rebuild AG headers and trees...
- agno = 0
traps: xfs_repair[4786] trap divide error ip:417fef sp:7ffe43770d60
error:0 in xfs_repair[400000+7a000]
Floating point exception
mount output:
XFS (dm-2): Mounting V5 Filesystem
XFS (dm-2): Corruption warning: Metadata has LSN (11:170112) ahead of
current LSN (1:64). Please unmount and run xfs_repair (>= v4.3) to
resolve.
XFS (dm-2): log mount/recovery failed: error -22
XFS (dm-2): log mount failed
mount: wrong fs type, bad option, bad superblock on /dev/mapper/storage-crypt,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
I dumped the whole volume with dd so that I can revert to the current
(hopefully not hopelessly screwed) state. Downloaded xfsprogs 4.11.0
and checked the changelog. There are fixes for xfs_repair phase 5,
though the FP exception is not mentioned. Is this bug already fixed?
Should I try xfs_repair from 4.11?
Thanks & kind regards, Peter
next reply other threads:[~2017-06-02 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 23:21 Péter András Felvégi [this message]
2017-06-05 8:57 ` My XFS volume died, please help! Carlos Maiolino
2017-06-05 17:29 ` Eric Sandeen
2017-06-07 11:11 ` Péter András Felvégi
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='CAG3eYYQMTdmCK9EdJA4hfYSSPStLSC=YBK+tvk67r6Vn4-UcxQ@mail.gmail.com' \
--to=petschy@gmail.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).