All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steffen D." <sdumke@gmail.com>
To: linux-xfs@vger.kernel.org
Subject: Fwd: mounting a xfs file system gives the message: "failure code -3003" and "structure needs cleaning"
Date: Mon, 31 Oct 2016 20:29:37 +0100	[thread overview]
Message-ID: <CAPvv1vx-Juge8e=36bq4AFvGxs8Kf7-V_v0j+a9LGWYdDo5h+w@mail.gmail.com> (raw)
In-Reply-To: <8bd7b65f-d85d-2958-dd7d-ba97c91ac9ea@telefonica.net>

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

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
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 0
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
disconnected inode 598004147, would move to lost+found
Phase 7 - verify link counts...
would have reset inode 598004147 nlinks from 0 to 1
No modify flag set, skipping filesystem flush and exiting.
linux-ibbi:/home/steffen #
----------

Any idea what to do? Or do have to use xfs_repair -L

Thanks a lot

Steffen


---------- Forwarded message ----------
From: Carlos E. R. <robin.listas@telefonica.net>
Date: 2016-10-30 21:45 GMT+01:00
Subject: Re: mounting a xfs file system gives the message: "failure
code -3003" and "structure needs cleaning"
To: linux-xfs@vger.kernel.org


On 2016-10-30 21:36, Steffen D. wrote:
> Hello list!
>
> I'll try to explain my problem:
>

> "inux-ibbi:/home/steffen # xfs_repair /dev/sda4
> Phase 1 - Superblock finden und =C3=BCberpr=C3=BCfen...
> Phase 2 - ein internes Protokoll benutzen

I don't know if it is too late, but to make things easier for the
experts here, it is better to run the command in English. Like this:




-- 
Signatur ausser Betrieb.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2016-10-31 19:29 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   ` Steffen D. [this message]
2016-10-31 19:42     ` Fwd: " Dave Chinner
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='CAPvv1vx-Juge8e=36bq4AFvGxs8Kf7-V_v0j+a9LGWYdDo5h+w@mail.gmail.com' \
    --to=sdumke@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 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.