public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Kingghost <mrlitres@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS_Repair PRoblem
Date: Fri, 7 Dec 2007 08:06:36 +1100	[thread overview]
Message-ID: <20071206210636.GM115527101@sgi.com> (raw)
In-Reply-To: <14194915.post@talk.nabble.com>

On Thu, Dec 06, 2007 at 08:10:21AM -0800, Kingghost wrote:
> 
> Hello,
> 
> So I was seeing my serial link go up and down so I rebooted and everything
> was working fine, except my vg0 wouldnt mount. So I tried to xfs_repair it
> and this is the output I recieved.
> 
> slutb0x:/# xfs_repair -o assume_xfs /dev/vg0/media 
> Phase 1 - find and verify superblock... 
> sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with
> calculated value 128 

NULLFSINO? Something has overwritten your superblock with a bunch of -1
values?

> resetting superblock root inode pointer to 128 
> sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with
> calculated value 129 
> resetting superblock realtime bitmap ino pointer to 129 
> sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with
> calculated value 130 
> resetting superblock realtime summary ino pointer to 130 
> Phase 2 - using internal log 
> - zero log... 

Uh-oh - you ran a xfs_repair -L, didn't you?
> 
> missing inbetween 
> 
> rebuilding directory inode 1225702584 
> bad hash table for directory inode 1342177425 (no data entry): rebuilding 

And a bunch of trashed directory structures...

> disconnected dir inode 752117670, moving to lost+found 
> disconnected inode 809433019, moving to lost+found 
> disconnected dir inode 823780059, moving to lost+found 
> disconnected dir inode 823780089, moving to lost+found 
> 
> fatal error -- creation of .. entry failed (117), filesystem may be out of
> space 

117 = EUCLEAN - corrupted filesystem. Sounds like there's more corruption
there than was discovered or the underlying disk is still corruption blocks.
What version of repair are you running ?

This is a dying disk you're trying to repair right?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-12-06 21:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 16:10 XFS_Repair PRoblem Kingghost
2007-12-06 21:06 ` David Chinner [this message]
2007-12-07  0:51   ` Kingghost
  -- strict thread matches above, loose matches on Subject: below --
2008-12-21 15:03 xfs_repair problem David Bernick
2008-12-21 15:55 ` Eric Sandeen
2008-12-21 16:52   ` David Bernick
2008-12-21 17:01     ` Eric Sandeen
2008-12-21 17:07       ` David Bernick
2008-12-21 22:08       ` David Bernick
2008-12-21 22:14         ` David Bernick
2008-12-21 22:20         ` Eric Sandeen
2008-12-21 17:12     ` Eric Sandeen

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=20071206210636.GM115527101@sgi.com \
    --to=dgc@sgi.com \
    --cc=mrlitres@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