From: Dave Chinner <david@fromorbit.com>
To: "Steffen D." <sdumke@gmail.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: Fwd: mounting a xfs file system gives the message: "failure code -3003" and "structure needs cleaning"
Date: Tue, 1 Nov 2016 06:42:12 +1100 [thread overview]
Message-ID: <20161031194212.GU14023@dastard> (raw)
In-Reply-To: <CAPvv1vx-Juge8e=36bq4AFvGxs8Kf7-V_v0j+a9LGWYdDo5h+w@mail.gmail.com>
On Mon, Oct 31, 2016 at 08:29:37PM +0100, Steffen D. wrote:
> Hello again
> thanks to Carlos for the hint about the language.
> Here are the messages in english:
> ----------
> linux-ibbi:/home/steffen # LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8
> xfs_repair /dev/sda4
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> ERROR: The filesystem has valuable metadata changes in a log which needs to
> be replayed. Mount the filesystem to replay the log, and unmount it before
> re-running xfs_repair. If you are unable to mount the filesystem, then use
> the -L option to destroy the log and attempt a repair.
> Note that destroying the log may cause corruption -- please attempt a mount
> of the filesystem before doing this.
> linux-ibbi:/home/steffen #
> ----------
>
> and
>
> ----------
> linux-ibbi:/home/steffen # LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8
> xfs_repair -n /dev/sda4
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - scan filesystem freespace and inode maps...
> Metadata corruption detected at block 0x1a1d6001/0x200
> flfirst 118 in agf 2 too large (max = 118)
> agf 118 freelist blocks bad, skipping freelist scan
> Metadata corruption detected at block 0x272c1001/0x200
> flfirst 118 in agf 3 too large (max = 118)
> agf 118 freelist blocks bad, skipping freelist scan
> agi unlinked bucket 51 is 61133235 in ag 2 (inode=598004147)
> sb_icount 349952, counted 357504
> sb_ifree 9426, counted 7433
> sb_fdblocks 9895143, counted 9426793
hmmm - AGFL sizing issue?
What is the error in dmesg when you try to mount the filesystem?
What hardware are you running on (cpu, ram, etc) and where/how was
this filesystem created? Did it come from another machine?
xfs_reapir -L should fix it, but I'd like to understand what the
problem was first and how it happened....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-10-31 19:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 20:36 mounting a xfs file system gives the message: "failure code -3003" and "structure needs cleaning" Steffen D.
2016-10-30 20:45 ` Carlos E. R.
2016-10-31 19:29 ` Fwd: " Steffen D.
2016-10-31 19:42 ` Dave Chinner [this message]
2016-10-31 20:20 ` Steffen D.
2016-10-31 20:37 ` Dave Chinner
2016-10-31 20:53 ` Steffen D.
2016-10-31 20:58 ` Dave Chinner
2016-10-31 21:09 ` Steffen D.
2016-10-31 21:25 ` Dave Chinner
2016-10-31 21:31 ` Carlos E. R.
[not found] ` <CAPvv1vxUW94s-NSkE9gXYLZLH=a-zP-2-r-fv=vhtMhQXeVX-A@mail.gmail.com>
[not found] ` <20161102204838.GD14023@dastard>
2016-11-02 21:05 ` Steffen D.
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=20161031194212.GU14023@dastard \
--to=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sdumke@gmail.com \
/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