From: Jyrki Muukkonen <jyrki.muukkonen@futurice.fi>
To: xfs@oss.sgi.com
Subject: xfs_repair: corrupt inode error
Date: Mon, 08 Jan 2007 12:23:32 +0200 [thread overview]
Message-ID: <1168251812.20568.8.camel@mustis> (raw)
Got this error in phase 6 when running xfs_repair 2.8.18 on ~1.2TB
partition over the weekend (it took around 60 hours to get to this
point :). On earlier versions xfs_repair aborted after ~15-20 hours with
"invalid inode type" error.
...
disconnected inode 4151889519, moving to lost+found
disconnected inode 4151889543, moving to lost+found
corrupt inode 4151889543 (btree). This is a bug.
Please report it to xfs@oss.sgi.com.
cache_node_purge: refcount was 1, not zero (node=0x132650d0)
fatal error -- 117 - couldn't iget disconnected inode
I've got the full log (both stderr and stdout) and can put that
somewhere if needed. It's about 80MB uncompressed and around 7MB
gzipped. Running the xfs_repair without multithreading and with -v might
also be possible if that's going to help.
--
Jyrki Muukkonen
Futurice Oy
jyrki.muukkonen@futurice.fi
+358 41 501 7322
next reply other threads:[~2007-01-08 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 10:23 Jyrki Muukkonen [this message]
2007-01-08 16:07 ` xfs_repair: corrupt inode error Jyrki Muukkonen
2007-01-12 1:25 ` Barry Naujok
2007-01-12 8:48 ` Jyrki Muukkonen
[not found] <200701142346.KAA16770@larry.melbourne.sgi.com>
2007-01-23 13:05 ` Jyrki Muukkonen
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=1168251812.20568.8.camel@mustis \
--to=jyrki.muukkonen@futurice.fi \
--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