xfs
[Top] [All Lists]

RE : xfs_repair fails with corrupt dinode

To: Brian Foster <bfoster@xxxxxxxxxx>
Subject: RE : xfs_repair fails with corrupt dinode
From: "SCHEFFER, Philippe" <Philippe.SCHEFFER@xxxxxxxx>
Date: Thu, 29 Jan 2015 23:09:48 +0100
Accept-language: fr-FR
Acceptlanguage: fr-FR
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20150129173414.GL17652@xxxxxxxxxxxxxx>
References: <587A9635632B174A943E53AF3B58A9082E3BE068CE@vanda>,<20150129173414.GL17652@xxxxxxxxxxxxxx>
Thread-index: AdA77GSkNxs6DW1oRcWjsxg8R78DOAAHcF1N
Thread-topic: xfs_repair fails with corrupt dinode
I join info in attached files.

Chronology:
Problem detected on FS.
FS unmounted
multiple xfs_repair -P  with message in my precedent mail
A try to remount FS give a kernel panic
FS is unmounted actually.  

Metadump compressed file is 1,4 Gb

Philippe
________________________________________
De : Brian Foster [bfoster@xxxxxxxxxx]
Date d'envoi : jeudi 29 janvier 2015 18:34
À : SCHEFFER, Philippe
Cc : xfs@xxxxxxxxxxx
Objet : Re: xfs_repair fails with corrupt dinode

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@xxxxxxxxxxxx
> 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@xxxxxxxxxxx
> http://oss.sgi.com/mailman/listinfo/xfs

Attachment: xfs_info.txt
Description: xfs_info.txt

Attachment: xfs_repair_P.log.gz
Description: xfs_repair_P.log.gz

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