From: Dave Chinner <david@fromorbit.com>
To: Dragon <Sunghost@gmx.de>
Cc: xfs@oss.sgi.com
Subject: Re: XFS Filesystem is broken and cant repair and mount!
Date: Fri, 10 Oct 2014 08:48:58 +1100 [thread overview]
Message-ID: <20141009214858.GF4376@dastard> (raw)
In-Reply-To: <trinity-ac293e2f-55d9-464e-8eab-f32026102118-1412890652269@3capp-gmx-bs22>
On Thu, Oct 09, 2014 at 11:37:32PM +0200, Dragon wrote:
> Hello Dave,
> and thx for reply. I have no backup and no disk todo this ;(.
> Here the result from xfs_repair -n:http://pastebin.com/jC5S0KSH
Looks like a handful of corrupted inode blocks, with the main
problem being that the inodes 3469995058-3469995060 (i.e. 3 inodes)
do not have the corect magic numbers in them. the rest of the inodes
in that chunk are corrupt in some way, too, so it would seem that
there's been some kind of write error to these inodes.
xfs_repair should fix this problems without issues.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-09 21:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 21:37 Re:XFS Filesystem is broken and cant repair and mount! Dragon
2014-10-09 21:48 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 20:54 XFS " Dragon
2014-10-12 20:56 ` Eric Sandeen
2014-10-12 22:16 ` Dave Chinner
2014-10-12 20:26 Dragon
2014-10-12 20:39 ` Eric Sandeen
2014-10-10 10:28 Dragon
2014-10-10 8:47 Dragon
2014-10-10 10:17 ` Emmanuel Florac
2014-10-09 22:42 Dragon
2014-10-10 10:07 ` Emmanuel Florac
2014-10-09 13:15 Dragon
2014-10-09 15:09 ` Eric Sandeen
2014-10-09 21:20 ` Dave Chinner
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=20141009214858.GF4376@dastard \
--to=david@fromorbit.com \
--cc=Sunghost@gmx.de \
--cc=xfs@oss.sgi.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