public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dr Peter A Barlow <peter@redcliffmicro.co.uk>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: corrupt dinode 4345, extent total = 1, nblocks = 0.  This is a bug.
Date: Fri, 04 May 2012 10:55:30 -0500	[thread overview]
Message-ID: <4FA3FBF2.1030508@sandeen.net> (raw)
In-Reply-To: <zarafa.4fa3b8af.2072.03b91b1f6d9ca76b@Solaris>

On 5/4/12 6:08 AM, Dr Peter A Barlow wrote:
> Hello,
> 
>  
> 
> I’ve received the following error..
> 
>  
> 
> /corrupt dinode 4345, extent total = 1, nblocks = 0.  This is a bug./
> 
> /Please capture the filesystem metadata with xfs_metadump and/
> 
> /report it to xfs@oss.sgi.com./
> 
> /cache_node_purge: refcount was 1, not zero (node=0x7f80593d8fc0)/
> 
> / /
> 
> /fatal error -- 117 - couldn't iget disconnected inode/
> 

First of all, are you using the latest xfsprogs?

> the zipped metadata is 60MB so emailing it is not feasible.

Is posting it somewhere feasible?

I'll contact you offlist with another idea.

-Eric

> Please advise as I am  desperate to recover my data.
> 
>  
> 
> Many thanks,
> 
>  
> 
> Peter.
> 
>  
> 
> 
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2012-05-04 15:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 11:08 corrupt dinode 4345, extent total = 1, nblocks = 0. This is a bug Dr Peter A Barlow
2012-05-04 15:55 ` Eric Sandeen [this message]

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=4FA3FBF2.1030508@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=peter@redcliffmicro.co.uk \
    --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