From: "Dr Peter A Barlow" <peter@redcliffmicro.co.uk>
To: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: corrupt dinode 4345, extent total = 1, nblocks = 0. This is a bug.
Date: Fri, 4 May 2012 12:08:31 +0100 [thread overview]
Message-ID: <zarafa.4fa3b8af.2072.03b91b1f6d9ca76b@Solaris> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 541 bytes --]
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
the zipped metadata is 60MB so emailing it is not feasible.
Please advise as I am desperate to recover my data.
Many thanks,
Peter.
[-- Attachment #1.2: Type: text/html, Size: 2912 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-05-04 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 11:08 Dr Peter A Barlow [this message]
2012-05-04 15:55 ` corrupt dinode 4345, extent total = 1, nblocks = 0. This is a bug 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=zarafa.4fa3b8af.2072.03b91b1f6d9ca76b@Solaris \
--to=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