public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Per Lundberg <perlun@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS: failed to read RT inodes
Date: Sat, 02 Feb 2008 09:53:42 -0600	[thread overview]
Message-ID: <47A49206.4020700@sandeen.net> (raw)
In-Reply-To: <8f1895b90802020212h278968efy7a644c55c480134e@mail.gmail.com>

Per Lundberg wrote:
> Hello,
> 
> After a hard drive failure (and no backup...) I am trying with all my
> strength do recover the file systems... With no real success. I have
> dumped over the two file systems in question to another, healthy disk
> drive. After dumping back the data to a third hard disk, one of the
> file system can be successfully mounted but with a huge number of
> files in the lost+found directory (after recovery using xfs_repair).
> Strange since the dump indicated only 11 bad sectors on that file
> system.
> 
> However, the big (55 gig) file system cannot even be mounted and this
> is troublesome since it contains the most valuable data. This is what
> I get after doing xfs_repair on the volume:
> 
> Jan 10 10:30:59 amos kernel: SGI XFS with ACLs, security attributes,
> realtime, large block numbers, no debug enabled
> Jan 10 10:30:59 amos kernel: SGI XFS Quota Management subsystem
> Jan 10 10:31:00 amos kernel: XFS mounting filesystem sda10
> Jan 10 10:31:00 amos kernel: XFS: failed to read RT inodes

maybe try xfs_db on the device; "sb 0" and "p" commands to see what the
rt inodes are.

-Eric

  reply	other threads:[~2008-02-02 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 10:12 XFS: failed to read RT inodes Per Lundberg
2008-02-02 15:53 ` Eric Sandeen [this message]
2008-02-02 19:01   ` Per Lundberg

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=47A49206.4020700@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=perlun@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