From: Eric Sandeen <sandeen@sandeen.net>
To: "Vitaly V. Ch" <vitaly.v.ch@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair refuse to repair my corrupted xfs partition
Date: Mon, 26 Jan 2009 12:30:59 -0600 [thread overview]
Message-ID: <497E0163.8010207@sandeen.net> (raw)
In-Reply-To: <6efe08af0901252337m22844fc2yee3cef2a8ed8ac6@mail.gmail.com>
Vitaly V. Ch wrote:
> Hi All!
...
> #xfs_repai /dev/loop0
> Phase 1 - find and verify superblock...
> Phase 2 - using internal log
> - zero log...
> - scan filesystem freespace and inode maps...
> - found root inode chunk
> Phase 3 - for each AG...
> - scan and clear agi unlinked lists...
> - process known inodes and perform inode discovery...
> - agno = 0
> entry "" in shortform directory 128 references invalid inode 0
> zero length entry in shortform dir 128, junking 3 entries
> corrected entry count in directory 128, was 3, now 0
> corrected directory 128 size, was 69, now 6
> bogus .. inode number (0) in directory inode 128, clearing inode number
> xfs_repair: dir2.c:2133: process_dir2: Assertion `(ino !=
> mp->m_sb.sb_rootino && ino != *parent) || (ino == mp->m_sb.sb_rootino
> && (ino == *parent || need_root_dotdot == 1))' failed.
>
>
> What I can do for repair my data? There was no hardware failure
you haven't said what version of xfs_repair you're using; if you are not
using the latest (2.10.2) please try that first.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-26 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 7:37 xfs_repair refuse to repair my corrupted xfs partition Vitaly V. Ch
2009-01-26 18:30 ` Eric Sandeen [this message]
2009-01-27 8:23 ` Vitaly V. Ch
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=497E0163.8010207@sandeen.net \
--to=sandeen@sandeen.net \
--cc=vitaly.v.ch@gmail.com \
--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