All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: "SCHEFFER, Philippe" <Philippe.SCHEFFER@inist.fr>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs_repair fails with corrupt dinode
Date: Thu, 29 Jan 2015 12:34:14 -0500	[thread overview]
Message-ID: <20150129173414.GL17652@laptop.bfoster> (raw)
In-Reply-To: <587A9635632B174A943E53AF3B58A9082E3BE068CE@vanda>

On Thu, Jan 29, 2015 at 04:48:15PM +0100, SCHEFFER, Philippe wrote:
> Hi,
> 
> I have a corrupted xfs filesytem. When I try to repair I get this error :
> disconnected inode 1427919, moving to lost+found
> corrupt dinode 1427919, 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=0x1f6c19620)
> 
> fatal error -- 117 - couldn't iget disconnected inode
> 
> I captured metada with xfs_metadump but the file is 1,4Gb long. I can't send it to you.
> 

What kernel/xfsprogs version, xfs_info, mount options? Do you have the
full xfs_repair output? In general:

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

It's not clear to me from your report whether repair fixed this or
failed itself. Also, can you compress the metadump image?

Brian

> I printed inode1427919 :
> 
> xfs_db> inode 1427919
> xfs_db> print
> core.magic = 0x494e
> core.mode = 0100644
> core.version = 2
> core.format = 2 (extents)
> core.nlinkv2 = 1
> core.onlink = 0
> core.projid_lo = 0
> core.projid_hi = 0
> core.uid = 1144
> core.gid = 1144
> core.flushiter = 19
> core.atime.sec = Fri Jan  9 21:50:25 2015
> core.atime.nsec = 132886289
> core.mtime.sec = Wed Oct 15 16:28:33 2014
> core.mtime.nsec = 166360243
> core.ctime.sec = Wed Oct 15 16:28:33 2014
> core.ctime.nsec = 166360243
> core.size = 2536
> core.nblocks = 1
> core.extsize = 0
> core.nextents = 1
> core.naextents = 0
> core.forkoff = 0
> core.aformat = 2 (extents)
> core.dmevmask = 0
> core.dmstate = 0
> core.newrtbm = 0
> core.prealloc = 0
> core.realtime = 0
> core.immutable = 0
> core.append = 0
> core.sync = 0
> core.noatime = 0
> core.nodump = 0
> core.rtinherit = 0
> core.projinherit = 0
> core.nosymlinks = 0
> core.extsz = 0
> core.extszinherit = 0
> core.nodefrag = 0
> core.filestream = 0
> core.gen = 837444118
> next_unlinked = null
> u.bmx[0] = [startoff,startblock,blockcount,extentflag] 0:[0,320660992,1,0]
> 
> What could I do for solve this problem.
> 
> Thanks in advance.
> 
> Philippe
> _______________________________________________
> 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:[~2015-01-29 17:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29 15:48 xfs_repair fails with corrupt dinode SCHEFFER, Philippe
2015-01-29 17:34 ` Brian Foster [this message]
     [not found]   ` <587A9635632B174A943E53AF3B58A9082E3BE068D0@vanda>
2015-01-29 22:56     ` RE : " Brian Foster
2015-01-29 23:45       ` Dave Chinner
2015-01-30  0:27         ` Brian Foster
2015-01-29 23:15 ` Dave Chinner
     [not found]   ` <587A9635632B174A943E53AF3B58A9082E3C81A6FB@vanda>
2015-01-30  5:52     ` RE : " Dave Chinner
2015-01-30 14:37       ` RE : " SCHEFFER, Philippe

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=20150129173414.GL17652@laptop.bfoster \
    --to=bfoster@redhat.com \
    --cc=Philippe.SCHEFFER@inist.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.