bug? "directory flags set on non-directory inode 2877105"

xfs

bug? "directory flags set on non-directory inode 2877105"

To:	xfs@xxxxxxxxxxx
Subject:	bug? "directory flags set on non-directory inode 2877105"
From:	Arkadiusz Miśkiewicz <arekm@xxxxxxxx>
Date:	Wed, 4 Jul 2012 17:59:05 +0200
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=maven.pl; s=maven; h=from:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:message-id; bh=/zGO9GdtE4qN1IBiVGImSBGg+sC0iniC2oI8EtN2lCk=; b=kj30PhNQN3Dx+jczWwJS3q6MifqtqbEuI4BXrwfGvwS4p04Fp+ZtB1psEOqb9lJYhp 2t18DfklDM2rBKhnlAr/3ky3zhKLUxxSuCCUhVTNNPslC+i1S9dklXWqH4K0NZfUKmTp J0BJ4hNu3mrTh1tu5tHEsoWrp6YWQG75FWWmY=
User-agent:	KMail/1.13.7 (Linux/3.5.0-rc5; KDE/4.8.4; x86_64; ; )

Hi.

On two servers using 3.0.x kernels I've got like 10 mln of "directory flags 
set on non-directory inode xxx" errors when doing xfs_repair. Doesn't look 
like a corruption issue, right?

Was there a bug in 2.6.3x or 3.0.x kernels that could get these flags set in 
such wrong way?

ps. using project quota on both servers/fses
-- 
Arkadiusz Miśkiewicz, arekm / maven.pl

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
bug? "directory flags set on non-directory inode 2877105", Arkadiusz MiÅkiewicz <= Re: bug? "directory flags set on non-directory inode 2877105", Dave Chinner Re: bug? "directory flags set on non-directory inode 2877105", Arkadiusz MiÅkiewicz

Previous by Date:	Re: [PATCH 2/2] xfs: do not call xfs_bdstrat_cb in xfs_buf_iodone_callbacks, Christoph Hellwig
Next by Date:	3.5.0-rc5: inconsistent lock state, Christian Kujau
Previous by Thread:	[PATCH 0/5] do not take the iolock in inode reclaim context, Christoph Hellwig
Next by Thread:	Re: bug? "directory flags set on non-directory inode 2877105", Dave Chinner
Indexes:	[Date] [Thread] [Top] [All Lists]