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:20:10 +1100 [thread overview]
Message-ID: <20141009212010.GE4376@dastard> (raw)
In-Reply-To: <trinity-c6202f4d-95cc-42f9-a8f2-86e3b9b231a9-1412860507253@3capp-gmx-bs31>
On Thu, Oct 09, 2014 at 03:15:07PM +0200, Dragon wrote:
> Hello, while i copy some files to my software raid device the xfs
> filesystem reports an uncorrectable error unmount and stops.
> Reboot didnt work, same failure. Answers to the FAQS:
>
> 1.Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
> 2.xfsprogs 3.1.7+b1 amd64
I'd upgrade xfsprogs before doing anything else.
> 13. dmesg:
> [ 7.541885] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
> [ 7.542692] SGI XFS Quota Management subsystem
> [ 7.569679] XFS (md2): Mounting Filesystem
> [ 7.799071] XFS (md2): Starting recovery (logdev: internal)
> [ 8.992087] XFS (md2): xlog_recover_inode_pass2: Bad inode magic number, dip = 0xffff88031c344400, dino bp = 0xffff88032050d0c0, ino = 3469995060
> [ 8.992354] XFS (md2): Internal error xlog_recover_inode_pass2(1) at line 2248 of file /build/linux-eKuxrT/linux-3.2.60/fs/xfs/xfs_log_recover.c. Caller 0xffffffffa03fe677
Bad inode cluster on disk. You need to run xfs_repair on the
filesystem.
I'd suggest running "xfs_repair -n" to see whether that's the only
error and whether it's likely to be able to repair without making a
mess. If you don't have backups, you might want to mount -o
ro,norecovery and take a backup before trying to repair properly.
If you're really paranoid, take a metadump of the filesystem,
restore themetadump to a file and see if repair can fix the image
file first.
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:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 13:15 XFS Filesystem is broken and cant repair and mount! Dragon
2014-10-09 15:09 ` Eric Sandeen
2014-10-09 21:20 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-09 21:37 Dragon
2014-10-09 21:48 ` XFS " Dave Chinner
2014-10-09 22:42 Dragon
2014-10-10 10:07 ` Emmanuel Florac
2014-10-10 8:47 Dragon
2014-10-10 10:17 ` Emmanuel Florac
2014-10-10 10:28 Dragon
2014-10-12 20:26 Dragon
2014-10-12 20:39 ` Eric Sandeen
2014-10-12 20:54 Dragon
2014-10-12 20:56 ` Eric Sandeen
2014-10-12 22:16 ` 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=20141009212010.GE4376@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