All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Paul Guermonprez <paul@guermonprez.eu>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair aborting ... dir2.c:2133
Date: Sat, 14 Jun 2008 11:51:27 -0500	[thread overview]
Message-ID: <4853F70F.6010400@sandeen.net> (raw)
In-Reply-To: <74d4a1e10806140124s3ed8dfa6x7e5ca656fea0e06e@mail.gmail.com>

Paul Guermonprez wrote:
> hello,
> 
> i have a xfs dump i want to repair under linux ubuntu.
> the partition was created by a storage system ss4000-e.

Do you mean that you did xfsrestore on a previous dump and then tried to
repair the resulting filesystem?  Maybe the dump was corrupt?

> if i use version 2.9.4, i have a segfault
> and version 2.9.8, the proces is aborted with message :
> 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.
> Aborted

If you are willing to provide an xfs_metadump image, Barry would
probably look into it for you :)

Did anything interesting go wrong before your fs got so mangled?

> i also tried to comment this test, but it returns a segfault just as
> version 2.9.4.
> 
> note :
> i already restored 3 xfs dumps from the same machine, and everything
> went in the lost+found, partly with no name, no directory, partly with
> a directory structure and filenames as expected.

xfsrestore did this?  that's pretty weird.

-Eric

> before xfs_repair, the mounted fs was empty, not even the ".." for root !
> 
> thanks, paul.
> 
> 

  reply	other threads:[~2008-06-14 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  8:24 xfs_repair aborting ... dir2.c:2133 Paul Guermonprez
2008-06-14 16:51 ` Eric Sandeen [this message]
2008-06-15 19:00   ` Paul Guermonprez

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=4853F70F.6010400@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=paul@guermonprez.eu \
    --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 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.