xfs
[Top] [All Lists]

Re: XFS: failed to read RT inodes

To: "Eric Sandeen" <sandeen@xxxxxxxxxxx>
Subject: Re: XFS: failed to read RT inodes
From: "Per Lundberg" <perlun@xxxxxxxxx>
Date: Sat, 2 Feb 2008 20:01:32 +0100
Cc: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=RXN4zfrK83KxRefUwD6+FtmL9N8ToMTjhIqvy4rW0pE=; b=kFCaPvGoSxPk9jEpKgMtVIEfmBSoCJmYB41NERsfbhfDDQuXubsT1Z1fzSXG699pdnHqi95yLc24yHbAi7tCeEWekVCmQo3kj4ub1HyW87dMwQxIr0+AP89h7sPqRae7kYwLJ9JC/Sk76jo6fVKKOouhKczifgYgGykCvGYnZZg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PnhvRS3V5UPgL4jfyAo2exHYIx3NGADQYK1yOikbWQOoh3JXsUhSOKegPiBNCqxmRvUAaip6WjVJiIJaEKHXQBtIoWqWr5KGLg9U4qyByhHGW5IxOJZO4mWxPIb+EKDfZSsQhAspy7znf0n0BVhyxcTrn6hyRmI8YQaa/OT0CNc=
In-reply-to: <47A49206.4020700@sandeen.net>
References: <8f1895b90802020212h278968efy7a644c55c480134e@mail.gmail.com> <47A49206.4020700@sandeen.net>
Sender: xfs-bounce@xxxxxxxxxxx
On Feb 2, 2008 4:53 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> > 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.

Thanks for the hint! However, what I did was do a full restore of the
volume again and then xfs_repair + xfs_repair -L. Now, I can mount it
- but *everything* (and I really mean literally everything) has been
put into lost+found. Slightly annoying to say the least, but still a
whole lot better than having lost it all.

I think it *could* be because of a bad imaging program (Image for
Windows). The first sector of the partition doesn't seem to come
through properly (after restore, it contains 512 0x00 bytes. Quite
wrong in other words, so that could be the reason for the breakage. I
guess I could put back the broken drive again and just "dd" over the
data to the working disk but when I tried to do that yesterday on
another partition, I got 500 or so bad sectors... compared to 11 with
Image for Windows. So either Image for Windows was lying to me or the
disk has been starting to fall apart even more. :-)
-- 
Best regards,
Per Lundberg


<Prev in Thread] Current Thread [Next in Thread>