linux-kernel - Re: XFS corruption on post 3.7 tree.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121213224119.GU30652@sgi.com>
Date:	Thu, 13 Dec 2012 16:41:19 -0600
From:	Ben Myers <bpm@....com>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Alex Elder <elder@...nel.org>, xfs@....sgi.com
Subject: Re: XFS corruption on post 3.7 tree.

Hi Dave,

On Thu, Dec 13, 2012 at 05:10:57PM -0500, Dave Jones wrote:
> On Thu, Dec 13, 2012 at 03:55:22PM -0500, Dave Jones wrote:
>  > Doing a kernel build while running on a 3.7+ tree from last night and I hit this...
>  > 
>  > 
>  > [22637.787422] XFS: Internal error XFS_WANT_CORRUPTED_RETURN at line 163 of file fs/xfs/xfs_dir2_data.c.  Caller 0xffffffffa070086a

Looks like the dir v2 verifier found that a single block directory had a data
entry without a corresponding leaf entry in the block.

> I unmounted, remounted, unmounted, and then ran xfs_repair on it, as prompted.
> xfs_repair noted..
> 
> bad hash table for directory inode 201328949 (bad stale count): rebuilding

Interesting!
								
> After remounting, things seemed ok again.
> I blew away my .ccache on that drive, and restarted my compile,
> and then hit the same bug again.

Suppose you could you grab a metadump before repairing it next time?  

Regards,
	Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/