xfs
[Top] [All Lists]

Re: Bug - xfs_repair asks me to report it

To: Björn Rafreider <bjoern_rafreider@xxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
Subject: Re: Bug - xfs_repair asks me to report it
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Fri, 03 Jan 2014 12:29:44 -0600
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <7ED0247242FEFB40BCA665733E613DCA0640C14C985D@xxxxxxxxxxxxxxxxx>
References: <7ED0247242FEFB40BCA665733E613DCA0640C14C985D@xxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
On 12/27/13, 6:42 AM, Björn Rafreider wrote:
> Hi,
> over christmas our backup system with XFS on LVM2 on iSCSI on Ubuntu 12.04.03 
> gave me several errors. Turned out, that the XFS was halted because of an 
> error. XFS_repair fixed several errors but finally quit with the following 
> error message:
> 
> corrupt dinode 3328159430, 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=0x1b928ab0)
> 
> fatal error -- couldn't map inode 3328159430, err = 117
> 
> the dump is running at the moment - but it already has 5G - little too big 
> for sending it by mail so I add a little more information

the metadump should compress quite well, for what it's worth.  Can you try?

-Eric

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Bug - xfs_repair asks me to report it, Eric Sandeen <=